News for hackers. Stuff that matters.

A comment on Why are my Go executable files so large?. Parent comment

Re:Why are my Go executable files so large? by loeg on Sunday December 29, 2019 @09:59PM (#21910434)
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

[2]: https://www.nongnu.org/libunwind/

[ Parent | on HN ]
Re:Why are my Go executable files so large? by saagarjha on Monday December 30, 2019 @02:42AM (#21911537)
I don’t think libunwind gives you function names if you strip symbols and don’t have debugging information on hand.
[ Parent | on HN ]
Re:Why are my Go executable files so large? by loeg on Monday December 30, 2019 @08:23PM (#21918230)
Sure. 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.
[ Parent | on HN ]