jeremy-rifkin
commented
11 months ago Hello, thank you for the report!
The first thing would probably be to check if the library is being built correctly and if the symbol actually exists in the library, for example on my machine
$ find . -name libcpptrace.so
./libcpptrace.so
$ nm ./libcpptrace.so | grep generate_trace
0000000000057873 T _ZN8cpptrace14generate_traceEjThere's a good chance the symbol could be discarded if the compiler thinks it's not used, which I ran into briefly on windows. There's a fix in #24 (which is a work-in-progress but hopefully can be merged soon) but I can apply a hot-fix on the main branch if needed.
CharlesJQuarra
Hi,
I successfully tested yesterday cpptrace on a test app with cmake and FetchContent_MakeAvailable. I went ahead to integrate it into a more complex cmake project using exactly the same strategy, but I kept getting
I tried literally everything I could think of to debug the issue: from adding the hardcoded path as
target_link_directoriesand hardcoding the-lcpptracewithtarget_link_options, to moving it around, with no luck.Needless to say, I checked the symbols are indeed present in the library:
I tried adding verbose options to the linker, but besides adding more contextual environment variables to the console output, there is really no hint on why it failed to find the linker reference
One of the libraries I'm depending was an older version of libtorch, and after reading a while, I noticed that since a few versions ago it started shipping with both pre-CXX11-ABI and CXX11-ABI builds, so just in case this was causing the incompatibility, I updated the libtorch version with one built with c++11 ABI, but the same problem keeps happening. In any case I tried this despite there is no hint the source of the linker failure was even remotely related to an ABI incompatibility, just because some people on the internet seemed to have similar mysterious undefined reference errors that were related to this.
I've tried to read more on how to debug linker errors, but it seems there is not a lot of available information short of becoming an amateur compiler developer myself. Do you have any better ideas how could I debug this error?
This is the linker command in question with lots of verbose output: