New comment by nekopsykose on void-packages repository https://github.com/void-linux/void-packages/issues/41159#issuecomment-1356699095 Comment: > The downside of using this implementation is that the abi is different meaning that all applications using libexecinfo will need to be recompiled. 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) > supposedly fixed 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) > fixing libexecinfo this isn't really possible, i don't think. the primary reason is in the linked mailing list discussion- without adding `eh_frame`, it's impossible for the execinfo backtrace to resolve inside the libc. but this sort of low level stuff isn't really something i specialise in, so don't take that as a 100% authoritative statement. on top of that, i'm not sure how well that backtrace works with `-fomit-frame-pointer -O2` on an executable. i don't remember in what scenarios it returned something non-empty, i'd have to look again.