This is the mail archive of the binutils@sourceware.org mailing list for the binutils 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]

Re: strip, Linux's backtrace_symbols API, and GCC optimizations levels


bgoodr3 <bgoodr@gmail.com> writes:

> Ian> That said, backtrace_symbols will not work
> Ian> reliably if called from a signal handler.
>
> Uh oh, ok, the backtrace_symbols man page says nothing of this
> limitation.  Can you provide more info as to why it is not reliable
> from a signal handler?

gcc does not generate correct unwind information from function
epilogues.  Therefore, if you get, say, a SIGPROF signal while executing
a function epilogue, backtrace from the signal handler will not work
correctly.

This is http://gcc.gnu.org/PR12990 and http://gcc.gnu.org/PR29997 .

Ian


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