From: Alexander Nyberg <alexn@telia.com>
To: Johnny Stenback <jst@jstenback.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gcc coredump with 2.6.12+ kernels
Date: Sat, 3 Sep 2005 19:40:31 +0200 [thread overview]
Message-ID: <20050903174030.GA5406@localhost.localdomain> (raw)
In-Reply-To: <4319DC91.4020406@jstenback.com>
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
next prev parent reply other threads:[~2005-09-03 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-03 17:25 gcc coredump with 2.6.12+ kernels Johnny Stenback
2005-09-03 17:40 ` Alexander Nyberg [this message]
2005-09-04 3:59 ` Johnny Stenback
2005-09-04 17:34 ` Johnny Stenback
2005-10-30 4:25 ` Johnny Stenback
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050903174030.GA5406@localhost.localdomain \
--to=alexn@telia.com \
--cc=jst@jstenback.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.