[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk

[Bug Watch Updater]

Launchpad has imported 2 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=396656.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2018-07-19T04:45:19+00:00 Karthik-datt wrote:

Created attachment 114009
Callgrind.out file is also attached

==967== Callgrind, a call-graph generating cache profiler

==967== Copyright (C) 2002-2015, and GNU GPL'd, by Josef Weidendorfer et
al.

==967== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright
info

==967== Command: /usr/share/WashingMachine/WashingMachineApp --platform
eglfs

==967==

==967== For interactive control, run 'callgrind_control -h'.

-967- WARNING: Serious error when reading debug info

-967- When reading debug info from /lib/ld-2.24.so:

-967-    debuginfo section duplicates a section in the main ELF file

-967- WARNING: Serious error when reading debug info

-967- When reading debug info from /lib/libgcc_s.so.1:

-967-    debuginfo section duplicates a section in the main ELF file

-967- WARNING: Serious error when reading debug info

-967- When reading debug info from /lib/libc-2.24.so:

-967-    debuginfo section duplicates a section in the main ELF file

-967- WARNING: Serious error when reading debug info

-967- When reading debug info from /lib/libpthread-2.24.so:

-967-    debuginfo section duplicates a section in the main ELF file

-967- WARNING: Serious error when reading debug info

-967- When reading debug info from /lib/libm-2.24.so:

-967-    debuginfo section duplicates a section in the main ELF file

-967- WARNING: Serious error when reading debug info

-967- When reading debug info from /lib/libdl-2.24.so:

-967-    debuginfo section duplicates a section in the main ELF file

-967- WARNING: Serious error when reading debug info

-967- When reading debug info from /lib/librt-2.24.so:

-967-    debuginfo section duplicates a section in the main ELF file

^C==967==

==967== Process terminating with default action of signal 2 (SIGINT)

==967==    at 0x4019678: ??? (in /lib/ld-2.24.so)

==967==

==967== Events    : Ir

==967== Collected : 12295033

==967==

==967== I   refs:      12,295,033

We are trying it on a Linux Arm platform , Imx6 Boundary devices Boards.

Tries it with 3.11 and also 3.13 version. Same warnings are thrown

Reply at:
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1848211/comments/0

------------------------------------------------------------------------
On 2019-11-28T15:28:34+00:00 Balint Reczey wrote:

Created attachment 124162
Don't look for debug alt file in debug image if it is already found

In a case observed in Ubuntu the duplicated section was .gnu_debuglink
and it is safe to ignore it like it is done for similar sections.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1848211/comments/6


** Changed in: valgrind
       Status: Unknown => New

** Changed in: valgrind
   Importance: Unknown => Medium

-- 
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 Committed
Status in valgrind source package in Focal:
  Fix Released
Status in valgrind package in Debian:
  Unknown

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