New comment by oreo639 on void-packages repository https://github.com/void-linux/void-packages/issues/41159#issuecomment-1356738883 Comment: Thank your so much for the clarifications. > the entire ABI is just the backtrace functions. if you mean the SONAME, that can freely be made to match. (i.e., there is no recompiling needed). (..maybe there was a stray other symbol? i remember seeing one, but nothing ever calls it in practice so an empty stub could be added) Yeah, my bad. When I was testing it with compiling ldc (libexecinfo is used by llvm12) I got: ``` Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_strptr: symbol not found Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: gelf_getehdr: symbol not found Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_begin: symbol not found Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: gelf_getsym: symbol not found Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_nextscn: symbol not found Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_getdata: symbol not found Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_version: symbol not found Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_end: symbol not found Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: gelf_getshdr: symbol not found Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_errmsg: symbol not found Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_errno: symbol not found ``` At the time I assumed that some function that used to be provided isn't being provided anymore, but yeah, that's definitely a different issue. > well.. it doesn't segfault, that's about all i can really say for it. it's a port of the latest version of libexecinfo from freebsd, which happens to have moved to libelf since the last one that was used (also a port) To be clear, what I meant by that was that I haven't really tested it due to the above issue. > i never found a point to have libexecinfo backtrace() Fair. It is currently required by LLVM for GWP-ASan. I personally had never used it (or heard of it) before looking into said issue. ~~That being said. I tried to use it with an intentional use-after-free which, for me, resulted in nothing happening. (with the current libexecinfo)~~ Edit: I do get the infinite loop in GWP-ASan. > on top of that, i'm not sure how well that backtrace works with `-fomit-frame-pointer -O2` on an executable I don't think we use `-fomit-frame-pointer`, correct me if I am wrong.