Closed Eternity1987 closed 4 months ago
Hi, this might be a simple issue of silently continuing on this error but a little additional information would be helpful. Did you compile with debug symbols?
I’ll also mention that the libbacktrace back-end is not recommended unless you have a good reason for using libbacktrace :)
I haven't been able to reproduce locally in debug however I have fixed this on the dev branch.
I compiled the release version and not with optimization flags , and I want to obtain at least the address function name and the corresponding binary in the release version, without the need for specific file names and line numbers, but it throw exception and return null_frame, will show 0x00
Ubuntu22.04 ok UUbuntu20.04 throw exception
Thanks. I think the patch should work for your use case, though it likely won't include function names without debug symbols.
I compiled libstacktrace.a from https://github.com/ianlancetaylor/libbacktrace on Ubuntu 20.04, and everything is fine.
Cpptrace internal error: Libbacktrace error:no debug info in ELF executable, code: -1