Objdump can't parse our Linux debug information about bitcoin HOT 6 CLOSED

This was already solved upstream!

Diff: https://sourceware.org/git/?p=binutils-gdb.git;a=blobdiff;f=binutils/objdump.c;h=3d70df470f290f7e4dc46cf80bc075f3015e6c14;hp=5acaa54929dbd4bbe37d7a2195ca698bfca603d0;hb=635d05b88f4823f46ef1ddbb3d438db16c0f6e71;hpb=5ce0e02478cc79a260c7e29822450284a32b9b12

i expect this will land in binutils 2.43. No need to keep this issue open.

from bitcoin.

Okay, may be a objdump bug actually?

readelf -wi (which should be equivalent to objdump -Wi) parses the same section fine. So does gdb it seems?

(FWIW i did try various versions of objdump before reporting this)

from bitcoin.

Closing for now.

edit: It's this objdump bug in dealing with compressed debug info sections: https://sourceware.org/bugzilla/show_bug.cgi?id=24319
which was supposedly fixed but... sigh

from bitcoin.

Reopening with more accurate title (phew).

Filed upstream issue: https://sourceware.org/bugzilla/show_bug.cgi?id=31692

from bitcoin.

Interestingly, the Windows build is unaffected. Maybe because of a different gcc/binutils?

This is probably because the Windows Binutils is configured without support for compressed debug sections, as it was, iirc, causing other windows build issues.

from bitcoin.

This is probably because the Windows Binutils is configured without support for compressed debug sections, as it was, iirc, causing other windows build issues.

Right, that makes sense. DWARF in PE binaires is a quite peculiar concept in the first place--heck, GNU even has its own way to encode the long section names needed: lief-project/LIEF#1043. i'm not surprised it's not set up to handle compressed sections.

from bitcoin.