On Wed, 2014-01-15 at 21:47 +0100, Jan Kratochvil wrote: > On Wed, 15 Jan 2014 16:16:34 +0100, Mark Wielaard wrote: > > - Maybe tweak the defaults for eu-stack based on feedback. > > Maybe use more debug information than just the line numbers if > > available (e.g. use the subprogram or inlined_subroutine names for the > > addresses found). > > There is also libbacktrace in GCC. But it has its own DWARF parser/handling. > libbacktrace needs just the raw PC unwound stack, it figures out DWARF and > inlined frames on its own. At least Fedora does not package libbacktrace yet.
I forgot about that one. It is completely different from what we provide since it was designed to be used in-process and doesn't actually do unwinding (it just uses the system/libgcc _Unwind_Backtrace to get the raw call stack). Since it is in-process and could be called from a signal handler it also needs to do everything in a signal safe way. But that just means that whatever they do, we can do but for different situations. I'll take a look to see if they use/provide the DWARF information in an interesting way that we could steal. Cheers, Mark
