public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: wwieser@gmx.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 05:26:00 -0000 [thread overview] Message-ID: <20021110132602.30462.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8511; it has been noted by GNATS. From: wwieser@gmx.de To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, reichelt@igpm.rwth-aachen.de Cc: Subject: Re: c++/8511: (hopefully) reproducible cc1plus SIGSEGV. Date: Sun, 10 Nov 2002 14:19:44 +0100 On Sunday 10 November 2002 00:54, reichelt@igpm.rwth-aachen.de wrote: > Synopsis: (hopefully) reproducible cc1plus SIGSEGV. > Thanks for your reply, but... > State-Changed-From-To: open->analyzed > State-Changed-By: reichelt > State-Changed-When: Sat Nov 9 15:54:52 2002 > State-Changed-Why: > Confirmed. > > Compiling the code with gcc 3.2 I get an internal compiler error. > The problem can be reduced to the following code snippet: > > ------------------------snip here-------------------- > [...] > ------------------------snip here-------------------- > > Compiling this with gcc 3.2 (just "g++ -c") I get the > following ICE: > > In fact, the short testcase crashes gcc since 2.95.x. > 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. 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. > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc& >pr=8511
next reply other threads:[~2002-11-10 13:26 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-10 5:26 wwieser [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 13:16 Volker Reichelt 2002-11-10 12:46 Zack Weinberg 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=20021110132602.30462.qmail@sources.redhat.com \ --to=wwieser@gmx.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).