[Bug 1848211]

[Mark J. Wielaard]

(In reply to Balint Reczey from comment #4)
> Please see the linked original bug for the reproducer.

I looked at
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1848211 but I
still don't fully understand how/why/when this happens.

There is some confusion because the patch is for .gnu_debugaltlink but
the bug talks about .gnu_debuglink (but I assume it really is the
altlink).

I think what would be helpful was an explanation of how dh_dwz works. It
looks like it runs dwz before the debuginfo is stripped into separate
files. Which might explain why things look garbled (it should be run on
the split .debug files of the package).

It looks like the original bug was on arm32 with ld.so. But later in the
bug report a x86_64 issue with glib2 library.

-- 
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:
  Won't Fix
Status in valgrind source package in Eoan:
  Fix Released
Status in valgrind source package in Focal:
  Fix Released
Status in valgrind package in Debian:
  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.
   * 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