https://bugs.kde.org/show_bug.cgi?id=427969
--- Comment #7 from Mark Wielaard <m...@klomp.org> --- (In reply to Austin English from comment #6) > (In reply to Mark Wielaard from comment #5) > > Thanks for including the files, this is really odd the main ELF file has > > both a .gnu_debuglink section and a .gnu_debugaltlink section, but no .debug > > sections itself. The .debug file itself also has a .gnu_debugaltlink. > > > > (Sidenote, the .gnu_debugaltlink is absolute, instead of a relative path > > from the .debug file, which makes it slightly harder to find unless you > > replicate the full file system layout.) > > > > This looks suspiciously like an Ubuntu bug: > > https://bugs.kde.org/show_bug.cgi?id=396656 > > I'm running Debian, not Ubuntu, to be clear, but fair enough. Should I > report this to Debian or should I gather some other information first? I assumed Debian and Ubuntu created the debuginfo packages the same way, but it seems that isn't true. At least not all of the time. It seems the issue in Ubuntu has been occurring for a longer time (since at least 2018), but the issue seems to have only occurred recently Debian packages. Do you happen to know if that observation is correct? And if so, what kind of change in debuginfo package creation might have caused this? In theory valgrind is right to reject a binary that has duplicate .gnu_debugaltlinks in both the main ELF and the separate .debug file. I don't mind working around it, but I have no idea how that can happen or whether we can rely on the .gnu_debugaltlinks being correct. So if you could find/report the issue in Debian and point me at that report, or point them at this report, so we can figure out what is going on, that would be perfect. -- You are receiving this mail because: You are watching all bug changes.
