public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manfred.rudigier at omicron dot at" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/62231] Exception handling broken on powerpc-e500v2-linux-gnuspe Date: Fri, 28 Nov 2014 12:53:00 -0000 [thread overview] Message-ID: <bug-62231-4-QSYC7zEz3L@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62231-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62231 --- Comment #3 from manfred.rudigier at omicron dot at --- I was probably to enthusiastic, the problem is still there, even in GCC 4.9.2. In order to reproduce the bug, you either have to use a root file system which was also built with GCC 4.8.3 or 4.9.2, or you just link the example program statically (which is probably the easier thing). The problem does not seem to be in the generated binary of the compiler, but in one of the used libs (probably libgcc_s.so). So when I link statically with the "-static" option, I got this stacktrace in gdb: Program received signal SIGABRT, Aborted. 0x1003d28c in raise () (gdb) bt #0 0x1003d28c in raise () #1 0x10018e1c in abort () #2 0x100100bc in uw_init_context_1 () #3 0x10010cdc in _Unwind_RaiseException () #4 0x10001db4 in __cxa_throw () at /home/manrud00/crosstool-ng/.build/src/gcc-4.9.2/libstdc++-v3/libsupc++/eh_throw.cc:82 #5 0x10000c94 in doThrow() () at exception.cpp:14 #6 0x10000cb8 in main () at exception.cpp:21
next prev parent reply other threads:[~2014-11-28 12:53 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-22 13:31 [Bug target/62231] New: " manfred.rudigier at omicron dot at 2014-11-27 5:16 ` [Bug target/62231] " asolokha at gmx dot com 2014-11-28 12:53 ` manfred.rudigier at omicron dot at [this message] 2014-11-28 17:20 ` [Bug target/62231] [4.8/4.9 regression] " ebotcazou at gcc dot gnu.org 2014-11-28 17:26 ` asolokha at gmx dot com 2014-12-01 12:32 ` rguenth at gcc dot gnu.org 2014-12-01 12:42 ` asolokha at gmx dot com 2014-12-19 13:26 ` jakub at gcc dot gnu.org 2014-12-22 8:55 ` manfred.rudigier at omicron dot at 2014-12-22 23:38 ` dan.wilder at watchguard dot com 2014-12-22 23:42 ` dan.wilder at watchguard dot com 2014-12-22 23:43 ` dan.wilder at watchguard dot com 2014-12-23 9:43 ` manfred.rudigier at omicron dot at 2015-05-19 18:01 ` andri.yngvason at marel dot com 2015-05-19 20:08 ` joseph at codesourcery dot com 2015-05-20 9:41 ` andri.yngvason at marel dot com 2015-06-23 8:16 ` rguenth at gcc dot gnu.org 2015-06-26 19:52 ` [Bug target/62231] [4.9 " jakub at gcc dot gnu.org 2015-06-26 20:26 ` jakub at gcc dot gnu.org
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=bug-62231-4-QSYC7zEz3L@http.gcc.gnu.org/bugzilla/ \ --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).