2 ms·
backtrace(3) doesn't use or understand DWARF debug information at all — it's purely a machine stack (doesn't understand tail calls or inlined functions) and can
by loeg 9y ago
backtrace(3) doesn't use or understand DWARF debug information at all — it's purely a machine stack (doesn't understand tail calls or inlined functions) and can only look up ELF symbols.
It's better than nothing, but consider using something like libunwind instead.
- mabynogy 9y agoMany thanks. I'll check it. The ultimate goal is to get a backtrace without debug symbol (in release) but I don't know any method to achieve that without instrumentation.
- loeg 9y agoYou need some debug information to get accurate backtraces. But you can discard the rest of the debug information that you don't need. The article actually mentions this a little bit near the end, starting around: > For example, if you would only like accurate unwinding then you can retain only .debug_frame and .debug_line.