public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8511: (hopefully) reproducible cc1plus SIGSEGV. Date: Sun, 10 Nov 2002 13:16:00 -0000 [thread overview] Message-ID: <20021110211601.24322.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8511; it has been noted by GNATS. From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> To: wwieser@gmx.de, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/8511: (hopefully) reproducible cc1plus SIGSEGV. Date: Sun, 10 Nov 2002 23:03:15 +0100 > The point is something different. I get a real SIGSEGV, NOT an internal > compiler error. Sadly, I have quite a lot of heavy template code which > triggers internal compiler errors (I reported one of them some time back > and it is not yet fixed), but this one really makes gcc SIGSEGV. I suppose it's *not* a "Internal compiler error: Segmentation fault". Did I get you rught? > Also, the debugger shows the suspicious address 0xa5a5a5a5 which might > indicate some more serious bug inside the compiler than simply a missing > C++ language feature. > So, please tell me if you can reproduce a SIGSEGV, and not an internal > compiler error. I just tried gcc 3.2 on your sources, but I only get an ICE. However, since you haven't provided a preprocessed source, I'm probably compiling different code than you. Can you generate a preprocessed source that also causes a segfault? If yes, could you please send the preprocessed file? If no, then something strange is happening :-( My first wild guess would be that the compiler ran out of memory when compiling your source. Can you make sure that this is not the reason (i.e. by using a swap device that is large enough)? You might have hardware problems: for example faulty memory (you could try to swap your chips if you have multiple banks of memory). I remember one PR where a faulty BIOS was responsible for strange gcc errors (are BIOS upgrades available for your board). Good luck, Volker PS: gcc-prs is a read-only list and therefore always bounces, just don't send any mail to that address. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8511
next reply other threads:[~2002-11-10 21:16 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-10 13:16 Volker Reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-22 10:46 Wolfgang Wieser 2002-11-20 18:16 Zack Weinberg 2002-11-20 18:12 Wolfgang Wieser 2002-11-19 18:25 Zack Weinberg 2002-11-19 18:16 Wolfgang Wieser 2002-11-10 12:46 Zack Weinberg 2002-11-10 5:26 wwieser 2002-11-09 15:54 reichelt 2002-11-09 4:36 wwieser
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=20021110211601.24322.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).