Hi, I'm in the following situation and need help understanding why valgrind doesn't show debug symbols. First of all, I'm on Linux 4.15 x86_64, valgrind 3.13.0. I'm running valgrind on ANGLE (angleproject.org). Normally, this library provides a .so file that I believe gets dynamically loaded, but a few of the tests statically link against this library.
Verification #1: I can verify that the executable I'm running is statically linked because ldd doesn't show a dependency to the library. I know the debug symbols are there. The code is built with -g2. Verification #2: Running gdb on the execution and breaking shows the symbols. `nm -l` shows the symbols and their paths as well. However, the stack traces I get from valgrind are of the following form: ==1199== at 0x61F1F89: sched_setaffinity@@GLIBC_2.3.4 (sched_setaffinity.c:35) ==1199== by 0x3B3D7F: ??? (in /path/to/angle_perftests) ==1199== by 0x326D02: ??? (in /path/to/angle_perftests) ==1199== by 0x38F6FC: ??? (in /path/to/angle_perftests) ==1199== by 0x39082F: ??? (in /path/to/angle_perftests) ==1199== by 0x390EC6: ??? (in /path/to/angle_perftests) ==1199== by 0x39CF86: ??? (in /path/to/angle_perftests) ==1199== by 0x39CAAB: ??? (in /path/to/angle_perftests) ==1199== by 0x37CB0D: ??? (in /path/to/angle_perftests) ==1199== by 0x610FB96: (below main) (libc-start.c:310) ==1199== Address 0x1ffefff9c8 is on thread 1's stack This doesn't match any of the possible outputs in question 4.2 of the faq (http://valgrind.org/docs/manual/faq.html)! If I run readelf -s, then I can see that many of the symbols are marked as HIDDEN under the Vis column (something for which I can't seem to find any documentation). Can anybody make sense of what's going on, or has any idea why valgrind is unable to give me debug symbols? Cheers, _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
