https://sourceware.org/bugzilla/show_bug.cgi?id=30980
--- Comment #2 from Mark Wielaard <mark at klomp dot org> --- This however is really odd and might explain why we get onto an ET_REL path: $ eu-readelf -x .gnu_debuglink ~/Downloads/libjavascriptcoregtk-4.1.so.0.4.10.zst Hex dump of section [28] '.gnu_debuglink', 84 bytes at offset 0x1fbedc8: 0x00000000 63727469 2e6f2e64 65627567 00000000 crti.o.debug.... 0x00000010 2aa4dad4 63727462 6567696e 532e6f2e *...crtbeginS.o. 0x00000020 64656275 67000000 39c05e5d 63727465 debug...9.^]crte 0x00000030 6e64532e 6f2e6465 62756700 6b271cc4 ndS.o.debug.k'.. 0x00000040 6372746e 2e6f2e64 65627567 00000000 crtn.o.debug.... 0x00000050 5fbdc21b _... So when looking for the separate .debug file, when we don't have a build-id match, we will search for crti.o.debug... -- You are receiving this mail because: You are on the CC list for the bug.