[Bug 1848211] Autopkgtest regression report (valgrind/1:3.15.0-1ubuntu3.1)
Ubuntu SRU Bot
1848211 at bugs.launchpad.net
Fri Nov 29 13:30:20 UTC 2019
All autopkgtests for the newly accepted valgrind (1:3.15.0-1ubuntu3.1) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:
apport/2.20.11-0ubuntu8.2 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#valgrind
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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:
Confirmed
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 Committed
Status in valgrind source package in Focal:
Fix Released
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.
* 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