On 28.09.2010 16:10, Julian Seward wrote: > It should just work, no problems. We've had debuginfo support for > years. Valgrind (well, Memcheck) won't even start up simple programs > on any recent Ubuntu without the debuginfo reader working, so it can't be > totally borked. FWIW, here's and example of what you should see > > --2280-- Reading syms from /lib/libc-2.11.1.so (0x5037000) > --2280-- Considering /lib/libc-2.11.1.so .. > --2280-- .. CRC mismatch (computed c73d5a83 wanted 02758e3e) > --2280-- Considering /usr/lib/debug/lib/libc-2.11.1.so .. > --2280-- .. CRC is valid > > Maybe there's some other problem here? Can gdb load the debuginfo > for /usr/lib/libpq.so.5.2 ?
I figured out that our debuginfo files no longer contain debug link (.gnu_debuglink section) in favour of build id (.note.gnu.build-id). The former caused some packaging issues and was replaced with build id solution which seems to be not supported by valgrind. As build id approach seems to be generally better and is fully supported by gdb it should also be supported by valgrind. Are there any plans to include it? Best regards, Jan Palus ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
