Maybe off topic?

Andi Kleen ak@muc.de
Fri Mar 26 12:12:00 GMT 1999


law@upchuck.cygnus.com (Jeffrey A Law) writes:

>   In message < vyz7ls4o9cg.fsf@issan.cs.uni-dortmund.de >you write:
>   > Glibc 2.1 has backtrace, declared in <execinfo.h>.
> I stand corrected then.   You learn something new every day ;-)

The glibc 2.1 backtrace on i386 only works when compiled without
-fomit-frame-pointer, and it does only resolve dynamically exported
symbols (so that the rest is left for addr2line). Extending it to
read the dwarf2 exception tables would be definitely a worthy goal,
to get accurate backtracing information even without standard stack
frame.

Is there a standard way on how user code can access these unwind 
tables without messing with libgcc2 internals? 

-Andi

-- 
This is like TV. I don't like TV.


More information about the Gcc mailing list