I am trying to get a Valgrind log without any missing debugging symbols (i.e. no '???' in any backtrace).
Currently, a part of my log is:
==34110== by 0x400F305: call_init.part.0 (dl-init.c:85) ==34110== by 0x400F3DE: _dl_init (dl-init.c:52) ==34110== by 0x40016E9: ??? (in /lib/x86_64-linux-gnu/ld-2.15.so)
apt-file search /lib/x86_64-linux-gnu/ld-2.15.so tells me that there is debugging information for the
$ apt-file search /lib/x86_64-linux-gnu/ld-2.15.so libc6: /lib/x86_64-linux-gnu/ld-2.15.so libc6-dbg: /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.15.so
So far so good, the problem is, this package is already installed on my system.
$ sudo apt-get install libc6-dbg Reading package lists... Done Building dependency tree Reading state information... Done libc6-dbg is already the newest version. The following packages were automatically installed and are no longer required: libklu1.1.0 libldl2.0.1 libcsparse2.2.3 libbtf1.1.0 Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Could someone explain why I still have missing symbols in ld.so? Is it a bug that should be reported?