This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/62231] Exception handling broken on powerpc-e500v2-linux-gnuspe


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]