3 ms·
libunwind[1][2] should unwind correctly if a compiler emits correct DWARF CFI unwind table (required by C++ w/ exceptions; available for C in gcc/clang with -fu
by loeg 7y ago
libunwind[1][2] should unwind correctly if a compiler emits correct DWARF CFI unwind table (required by C++ w/ exceptions; available for C in gcc/clang with -funwind-tables).
[1]: https://github.com/llvm-mirror/libunwind https://github.com/llvm-mirror/libunwind
[2]: https://www.nongnu.org/libunwind/ https://www.nongnu.org/libunwind/
- saagarjha 7y agoI don’t think libunwind gives you function names if you strip symbols and don’t have debugging information on hand.
- loeg 7y agoSure. libunwind is taking the place of pclntab here, not the symbol table. Go must also not strip symbols in order to print backtraces; if you want the same thing in C, don't strip the symbol table there either.