Displaying 1 result from an estimated 1 matches for "_unwind_raise_exception".
Did you mean:
__unwind_raiseexception
2010 Feb 20
1
[LLVMdev] Generating a backtrace
...x406f25
0x407158
Function _Unwind_RaiseException
0x401359
0x401ead
0x406155
0x4060a6
0x4020c6
Function __libc_start_main
0x400e09
The hex values are ones where dladdr() failed to provide a function name. As
you can see, the only functions it was able to deal with are the libc
startup function, and _Unwind_Raise_Exception itself. Yet I know these
functions have symbolic names, since I can step through them in gdb, set
breakpoints, and so on.
I've tried a number of other approaches: Calling dlopen(NULL) and then using
dlsym() to try and locate __data_start so that I can then attempt to
manually parse the DWARF d...