[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk
Launchpad Bug Tracker
1848211 at bugs.launchpad.net
Mon Dec 9 08:20:39 UTC 2019
This bug was fixed in the package valgrind - 1:3.15.0-1ubuntu3.1
---------------
valgrind (1:3.15.0-1ubuntu3.1) eoan; urgency=medium
* Don't look for debug alt file in debug image if it is already found
(LP: #1848211)
-- Balint Reczey <rbalint at ubuntu.com> Wed, 27 Nov 2019 13:52:54 +0100
** Changed in: valgrind (Ubuntu Eoan)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to valgrind in Ubuntu.
https://bugs.launchpad.net/bugs/1848211
Title:
[SRU] valgrind fails to use debug symbols from glib/gtk
Status in Valgrind:
New
Status in valgrind package in Ubuntu:
Fix Released
Status in valgrind source package in Bionic:
Triaged
Status in valgrind source package in Disco:
Triaged
Status in valgrind source package in Eoan:
Fix Released
Status in valgrind source package in Focal:
Fix Released
Status in valgrind package in Debian:
Confirmed
Bug description:
[Impact]
* With dwz the .gnu_debuglink section may appear duplicated in the
debug file referenced originally in the .gnu_debuglink section. In
that case Valgrind fails to load the debug symbols.
[Test Case]
* In Ubuntu releases earlier than 19.10 use gio from a package rebuilt with dwz.
* Install debug symbols for gio following the guide at https://wiki.ubuntu.com/Debug%20Symbol%20Packages
* Observe no relevant error when running gio with valgrind:
$ valgrind /usr/bin/gio ~
[Regression Potential]
* The fix is very simple, just ignoring the second .gnu_debuglink
found. There are no likely regressions.
[Original Bug Text]
The debug symbols from libglib2.0-0-dbgsym and libgtk-3-0-dbgsym don't
get properly picked up by valgrind in eoan for some reason. The
symbols correctly work under gdb.
There is an warning printed from valgrind
'debuginfo section duplicates a section in the main ELF file'
Laney tried to rebuild without dh_dwz and it makes the warning go away and the symbol work.
Downgrading valgrind to the disco version doesn't fix the issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/valgrind/+bug/1848211/+subscriptions
More information about the foundations-bugs
mailing list