(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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848211 Title: [SRU] valgrind fails to use debug symbols from glib/gtk To manage notifications about this bug go to: https://bugs.launchpad.net/valgrind/+bug/1848211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
