Package: valgrind Version: 1:3.8.1-2 Severity: important Tags: upstream Control: found -1 1:3.8.1-1
Dear Debian folks,
I paste my message to the valgrind-users list [0] which unfortunately
nobody replied to.
--- begin paste ---
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?
--- end paste ---
Asking about this in the IRC channels on <irc.oftc.net> I was told that
other people have experienced this too but nobody reported it yet. I
have no idea how to debug this as Valgrind reports in the beginning to
have found the symbols. Also I have not yet found a clue what is
triggering this (multiarch?) as for some libraries showing the line
numbers works fine.
Thanks,
Paul
[0]
http://sourceforge.net/mailarchive/forum.php?thread_name=1360582355.14992.91.camel%40mattotaupa&forum_name=valgrind-users
[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
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages valgrind depends on:
ii libc6 2.13-38
ii libc6-dbg 2.13-38
Versions of packages valgrind recommends:
ii gdb 7.4.1+dfsg-0.1
ii valgrind-dbg 1:3.8.1-2
Versions of packages valgrind suggests:
pn alleyoop <none>
pn kcachegrind <none>
pn valgrind-mpi <none>
pn valkyrie <none>
-- no debconf information
signature.asc
Description: This is a digitally signed message part
