public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jgrimm2 at us dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/19916] New: Segmentation fault in __static_initialization_and_destruction_0 Date: Sat, 12 Feb 2005 14:07:00 -0000 [thread overview] Message-ID: <20050211225624.19916.jgrimm2@us.ibm.com> (raw) The following testcase segfaults on 3.4.4 and 3.4.0, but runs to completion on 3.2.3. Note this test won't even compile on mainline, so I don't know if the same problem exists there. See: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19878 -------------------------------------------------------- //test.c struct S { char k; }; char const volatile S::* const p01 = &S::k; int main(void) { return 0; } -------------------------------------------------------- /opt/gcc-nightly/3.4-20050211/bin/g++ -o test test.c ./test Segmentation fault ------------------------------------------------ $ gdb ./test (gdb) run Starting program: /home/jgrimm/tmp/13930/test Program received signal SIGSEGV, Segmentation fault. 0x10000474 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at g.c:5 5 char const volatile S::* const p01 = &S::k; ----------------------------------------------- $ /opt/gcc-nightly/3.4-20050211/bin/g++ -v Reading specs from /home/gcc-nightly/3.4-20050211/bin/../lib/gcc/powerpc64-linux/3.4.4/specs Configured with: /home/gccbuild/gcc_3.4_anoncvs/gcc/configure --prefix=/opt/gcc-nightly/3.4-20050211 --build=powerpc64-linux --host=powerpc64-linux --target=powerpc64-linux --with-cpu=default32 --with-as=/opt/gcc-nightly/binutils/bin/as --with-ld=/opt/gcc-nightly/binutils/bin/ld --enable-threads=posix --enable-shared --enable-__cxa_atexit --enable-languages=c,c++,f77,java,objc Thread model: posix gcc version 3.4.4 20050211 (prerelease) -- Summary: Segmentation fault in __static_initialization_and_destruction_0 Product: gcc Version: 3.4.4 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jgrimm2 at us dot ibm dot com CC: gcc-bugs at gcc dot gnu dot org GCC host triplet: ppc64-unknown-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19916
next reply other threads:[~2005-02-11 22:56 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-12 14:07 jgrimm2 at us dot ibm dot com [this message] 2005-02-12 15:06 ` [Bug c++/19916] [3.4/4.0? Regression] " pinskia at gcc dot gnu dot org 2005-02-16 19:19 ` pinskia at gcc dot gnu dot org 2005-02-16 19:26 ` pinskia at gcc dot gnu dot org 2005-02-24 14:05 ` [Bug c++/19916] [3.4/4.0 " mmitchel at gcc dot gnu dot org 2005-02-24 14:05 ` [Bug c++/19916] [3.4/4.0? " mmitchel at gcc dot gnu dot org 2005-03-02 17:13 ` [Bug c++/19916] [3.4/4.0/4.1 " cvs-commit at gcc dot gnu dot org 2005-03-02 20:56 ` cvs-commit at gcc dot gnu dot org 2005-03-02 20:58 ` cvs-commit at gcc dot gnu dot org 2005-03-02 21:04 ` mmitchel at gcc dot gnu dot org 2005-03-07 16:04 ` jgrimm2 at us dot ibm dot com
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=20050211225624.19916.jgrimm2@us.ibm.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).