Re: gcc coredump with 2.6.12+ kernels

[Alexander Nyberg]

On Sat, Sep 03, 2005 at 10:25:37AM -0700 Johnny Stenback wrote:

> Hey all,
> 
> I just attempted to upgrade my kernel to 2.6.13. The kernel appears to 
> boot and run just fine, but when I try to build any larger projects like 
> Mozilla or the Linux kernel I constantly get segfaults from gcc. All 
> other apps *seem* to work fine. I remember seeing this with 2.6.12 too 
> when I tried to upgrade to it too but I didn't have the time to 
> investigate at all then, but now I see the same problem with 2.6.13. The 
> last version I've used that didn't show this problem is 2.6.11.3, and 
> that's running with no problems here.
> 
> When gcc segfaults I get the following messages in the messages log:
> 
> cc1[16775]: segfault at 0000000000000000 rip 00000036f2b0119e rsp 
> 00007fffffaaf0a0 error 4
> cc1[17086]: segfault at 0000000000000000 rip 00000036f2b0119e rsp 
> 00007fffffc4dfc0 error 4
> cc1[17788]: segfault at 0000000000000000 rip 00000036f2b0119e rsp 
> 00007fffffd777e0 error 4
> cc1[17823]: segfault at 0000000000000000 rip 00000036f2b0119e rsp 
> 00007fffffc4d630 error 4
> cc1[17895]: segfault at 0000000000000000 rip 00000036f2b0119e rsp 
> 00007ffffffd2330 error 4
> 
> I'm on a dual AMD Opteron system, running x86_64 code. Using Fedora Core 
> 2 (yeah, old, I know...) and gcc 3.3.3 20040412.

Does it still happen if you run:

echo 0 > /proc/sys/kernel/randomize_va_space
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/