|
From: Paul M. <pau...@us...> - 2013-02-11 11:32:47
|
Dear Valgrind users,
first a big thank you to the developers for this great program.
I am using Valgrind 3.8.1-1 from Debian Sid/unstable.
Despite having the debug packages of some packages installed for the
debug symbols and Valgrind finding them, it does not give the line
number. The strange thing is, that GDB has no problems with this and is
able to display the source file and file name just fine.
Two programs this happened with are Evolution [1][2] and HPLIP while
running Simple Scan under Valgrind.
Here Valgrind seems to find the file with debugging symbols.
--19364-- Reading syms from /usr/lib/libhpip.so.0.0.1
--19364-- Considering /usr/lib/debug/.build-id/84/1c797c37116c1c9365f12b531eec5dc65ebab1.debug ..
--19364-- .. build-id is valid
But it does not give me the line number in the source file.
==19364== Conditional jump or move depends on uninitialised value(s)
==19364== at 0x20ED4E25: ipConvert (in /usr/lib/libhpip.so.0.0.1)
==19364== by 0x20EB7595: sclpml_read (in /usr/lib/sane/libsane-hpaio.so.1.0.0)
==19364== by 0x424595: _scanner_scan_thread_gthread_func (scanner.c:7155)
I read the entry in the FAQ [3], but I have the debugging symbols
installed.
If Valgrind is using some different mechanism than GDB to find out the
source file and line number, how can I check that the files containing
debugging symbols adhere to Valgrind’s requirements?
Thanks,
Paul
[1] https://mail.gnome.org/archives/evolution-hackers/2013-January/msg00020.html
[2] https://bugzilla.gnome.org/show_bug.cgi?id=691303
[3] http://valgrind.org/docs/manual/faq.html#faq.unhelpful
|