Activity log for bug #1848211

Date Who What changed Old value New value Message
2019-10-15 14:10:20 Sebastien Bacher bug added bug
2019-10-15 15:43:30 Iain Lane tags rls-ee-incoming rls-ff-incoming
2019-10-15 15:43:54 Iain Lane valgrind (Ubuntu): status New Triaged
2019-10-15 15:43:57 Iain Lane valgrind (Ubuntu): importance Undecided High
2019-10-24 16:48:51 Brian Murray nominated for series Ubuntu Focal
2019-10-24 16:48:51 Brian Murray bug task added valgrind (Ubuntu Focal)
2019-10-24 16:49:07 Brian Murray tags rls-ee-incoming rls-ff-incoming rls-ee-incoming
2019-10-25 09:06:48 Iain Lane bug watch added https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942614
2019-10-25 09:06:48 Iain Lane bug task added valgrind
2019-10-25 10:48:14 Bug Watch Updater valgrind: status Unknown Confirmed
2019-10-26 12:28:26 Francis Ginther tags rls-ee-incoming id-5db1d566ba640b107bc522cd rls-ee-incoming
2019-11-21 15:51:15 Brian Murray tags id-5db1d566ba640b107bc522cd rls-ee-incoming id-5db1d566ba640b107bc522cd
2019-11-21 15:51:21 Brian Murray nominated for series Ubuntu Eoan
2019-11-21 15:51:21 Brian Murray bug task added valgrind (Ubuntu Eoan)
2019-11-21 15:51:32 Brian Murray valgrind (Ubuntu Eoan): status New Triaged
2019-11-21 15:51:34 Brian Murray valgrind (Ubuntu Eoan): importance Undecided High
2019-11-28 14:59:54 Balint Reczey description 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. [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.
2019-11-28 15:00:52 Balint Reczey summary valgrind fails to use debug symbols from glib/gtk [SRU] valgrind fails to use debug symbols from glib/gtk
2019-11-28 15:04:23 Balint Reczey nominated for series Ubuntu Bionic
2019-11-28 15:04:23 Balint Reczey bug task added valgrind (Ubuntu Bionic)
2019-11-28 15:04:23 Balint Reczey nominated for series Ubuntu Disco
2019-11-28 15:04:23 Balint Reczey bug task added valgrind (Ubuntu Disco)
2019-11-28 15:04:32 Balint Reczey valgrind (Ubuntu Bionic): importance Undecided Low
2019-11-28 15:04:38 Balint Reczey valgrind (Ubuntu Disco): importance Undecided Low
2019-11-28 15:13:01 Balint Reczey valgrind (Ubuntu Bionic): status New Triaged
2019-11-28 15:13:04 Balint Reczey valgrind (Ubuntu Disco): status New Triaged
2019-11-28 15:30:27 Balint Reczey bug watch added https://bugs.kde.org/show_bug.cgi?id=396656
2019-11-29 02:34:15 Launchpad Janitor valgrind (Ubuntu Focal): status Triaged Fix Released
2019-11-29 09:41:12 Balint Reczey valgrind (Ubuntu Eoan): status Triaged In Progress
2019-11-29 09:41:20 Balint Reczey valgrind (Ubuntu Eoan): assignee Balint Reczey (rbalint)
2019-11-29 09:41:24 Balint Reczey valgrind (Ubuntu Focal): assignee Balint Reczey (rbalint)
2019-11-29 11:41:00 Timo Aaltonen valgrind (Ubuntu Eoan): status In Progress Fix Committed
2019-11-29 11:41:02 Timo Aaltonen bug added subscriber Ubuntu Stable Release Updates Team
2019-11-29 11:41:05 Timo Aaltonen bug added subscriber SRU Verification
2019-11-29 11:41:08 Timo Aaltonen tags id-5db1d566ba640b107bc522cd id-5db1d566ba640b107bc522cd verification-needed verification-needed-eoan
2019-12-01 05:47:28 Mathew Hodson bug task added valgrind (Debian)
2019-12-01 05:48:11 Mathew Hodson valgrind: status Confirmed Unknown
2019-12-01 05:48:11 Mathew Hodson valgrind: remote watch Debian Bug tracker #942614 KDE Bug Tracking System #396656
2019-12-01 17:23:38 Bug Watch Updater valgrind: status Unknown New
2019-12-01 17:23:38 Bug Watch Updater valgrind: importance Unknown Medium
2019-12-01 19:33:07 Bug Watch Updater valgrind (Debian): status Unknown Confirmed
2019-12-03 16:05:46 Balint Reczey 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. [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.
2019-12-03 16:10:49 Balint Reczey tags id-5db1d566ba640b107bc522cd verification-needed verification-needed-eoan id-5db1d566ba640b107bc522cd verification-done verification-done-eoan
2019-12-09 08:20:39 Launchpad Janitor valgrind (Ubuntu Eoan): status Fix Committed Fix Released
2019-12-09 08:20:44 Łukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team
2020-06-30 14:12:56 Bug Watch Updater valgrind (Debian): status Confirmed Fix Released
2020-07-02 19:55:22 Steve Langasek valgrind (Ubuntu Disco): status Triaged Won't Fix
2021-03-10 01:44:03 Bug Watch Updater valgrind: status New Fix Released
2021-03-10 01:44:06 Bug Watch Updater bug watch added https://bugs.kde.org/show_bug.cgi?id=427969
2021-03-10 03:26:36 Dominicusin bug added subscriber Dominicusin