| 1 |
On Tue, Sep 13, 2005 at 03:24:38PM +0200, Frank Schafer wrote: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> this bug is from 2005-02-05. It was reported again (in this thread) |
| 5 |
> 2005-02-10. I hit the same behavior 2005-09-08. |
| 6 |
> |
| 7 |
> internal compiler error: segmentation fault during emerge Xorg |
| 8 |
> |
| 9 |
> The bug is simply reproducible (emerge Xorg) at the same line of code. |
| 10 |
> |
| 11 |
> The bug is still marked as NEW. Donnie Berkholz replied 2005-02-10 with: |
| 12 |
> "Could you humor me and try with a vanilla kernel?" |
| 13 |
> |
| 14 |
> My questions here: Does someone have a look at this? I think a not |
| 15 |
> installable Xorg is severe enough to mark it as CRITICAL. |
| 16 |
> |
| 17 |
> Does someone know if it's worth a try with the vanilla and if vanilla |
| 18 |
> here means a really vanilla from kernel.org or if it's sufficient to get |
| 19 |
> the (too patched and thus not so vanilla) vanilla-sources. |
| 20 |
> |
| 21 |
> Please be kind with me regarding to the fact that I'm posting here. On |
| 22 |
> the gentoo mailing list I get only replies like: "You probably have |
| 23 |
> faulty memory." If THIS would be the fact the bug would show up randomly |
| 24 |
> in different ebuilds or at least at different lines of code. |
| 25 |
|
| 26 |
Granted Donnie is a miserable so and so, but his advice is |
| 27 |
accurate. |
| 28 |
|
| 29 |
To get an ICE (what you're getting) requires either |
| 30 |
1) faulty hardware. proc going nuts, mem going nuts |
| 31 |
2) faulty kernel |
| 32 |
3) faulty toolchain |
| 33 |
|
| 34 |
Reproducability of a failure across reboots kind of indicates 1 as not |
| 35 |
being the case, leaving 2, and 3. |
| 36 |
|
| 37 |
ICE's are pretty much *never* the fault of the source; the source may |
| 38 |
expose a toolchain bug, but it's not the sources fault. |
| 39 |
|
| 40 |
You don't blame an email for crashing your email client, you blame your |
| 41 |
email client for horking up and segfaulting, instead of gracefully |
| 42 |
failing in the face of potentially wrong input. |
| 43 |
|
| 44 |
Note I'm not stating the source is the fault here, just trying to |
| 45 |
clarify that ICE's pretty much are indicative of |
| 46 |
hardware/kernel/toolchain being nuts, not the source that's being |
| 47 |
compiled. |
| 48 |
|
| 49 |
So... try his suggestion. Yes it's annoying, but frankly addressing |
| 50 |
your issues here pretty much requires poking at the options above, |
| 51 |
seeing if one of them makes compilation stop ICE'ing. If it does, |
| 52 |
then you back track and figure out what changed... etc. |
| 53 |
~harring |
Archives