From: | "Bo Ørsted Andresen" <bo.andresen@××××.dk> | ||
---|---|---|---|
To: | gentoo-user@l.g.o | ||
Subject: | Re: [gentoo-user] Segmentation fault on Emerge -S | ||
Date: | Thu, 12 Oct 2006 09:05:41 | ||
Message-Id: | 200610121058.21689.bo.andresen@zlin.dk | ||
In Reply to: | [gentoo-user] Segmentation fault on Emerge -S by Wagner Vaz |
1 | On Thursday 12 October 2006 09:59, Wagner Vaz wrote: |
2 | > It's a bit funny if not sad. Just look: |
3 | > |
4 | > #emerge -S netrw |
5 | > Searching... |Segmentation fault |
6 | > |
7 | > What is these? |
8 | |
9 | It really would help if we knew what version you were running. Try this: |
10 | |
11 | # emerge -u portage |
12 | |
13 | # emerge -u python |
14 | |
15 | # python-updater |
16 | |
17 | # revdep-rebuild |
18 | |
19 | If after that you still see the above behaviour: |
20 | |
21 | # emerge --debug -S netrw &> debug.log |
22 | # gzip debug.log |
23 | |
24 | Then attach debug.log.gz and post that together with the output of: |
25 | |
26 | # emerge --info |
27 | |
28 | -- |
29 | Bo Andresen |
Subject | Author |
---|---|
Re: [gentoo-user] Segmentation fault on Emerge -S | Wagner Vaz <wagvaz@×××××.com> |