|
From: Jan P. <jan...@gm...> - 2010-09-24 17:03:37
|
Hi, I'm trying to figure out how to use debuginfo files with valgrind but I have no clue what can I do more. I didn't found any specific documentation about this, except that it should work ootb. Runing valgrind with -d -v -v -v does not show any attempts to load any debug info files. Regarding symbol tables there's only something like: --8129-- Reading syms from /usr/lib/libpq.so.5.2 (0x4b08000) --8129-- object doesn't have a symbol table I have no idea whether it's relevant or not, but I guess the attempt to load debug info file should be somewhere around here. What's more gdb works perfectly ok after using add-symbol-file command. Is there any special option for debug info files? Is my system screwed? Thanks in advance for any help. I tried both valgrind 3.5.0 and svn snapshot 11368. Best regards, Jan Palus |
|
From: Julian S. <js...@ac...> - 2010-09-28 14:12:55
|
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 ? J On Friday, September 24, 2010, Jan Palus wrote: > Hi, > > I'm trying to figure out how to use debuginfo files with valgrind but I > have no clue what can I do more. I didn't found any specific > documentation about this, except that it should work ootb. Runing > valgrind with -d -v -v -v does not show any attempts to load any debug > info files. Regarding symbol tables there's only something like: > > --8129-- Reading syms from /usr/lib/libpq.so.5.2 (0x4b08000) > --8129-- object doesn't have a symbol table > > I have no idea whether it's relevant or not, but I guess the attempt to > load debug info file should be somewhere around here. What's more gdb > works perfectly ok after using add-symbol-file command. Is there any > special option for debug info files? Is my system screwed? Thanks in > advance for any help. > > I tried both valgrind 3.5.0 and svn snapshot 11368. > > > 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 > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Jan P. <jan...@gm...> - 2010-10-01 18:22:51
|
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 |