Binutils 2.17 objdump Broken

[bonefish]

Binutils 2.17 objdump (070218 gcc package from BeBits) crashes when disassembling (gcc 2.95.3 generated) objects with debug info (objdump -D --demangle ...). Can be reproduced under both Haiku and BeOS.

I tracked down one problem to a dereferenced NULL pointer in opcodes/i386-dis.c:print_insn() (first putop() call). Apparently the bug has already been fixed in CVS version 1.132 (2007/08/02 00:40:02) of the file.

I get a different stack trace for another test file (libperl.so compiled with "-g") though, so it seems not to be the only problem.

Update to newer binutils recommended.

[bonefish]

I gave the binutils 2.18 a try, but merging the eh-frame stuff scared the shit out of me. Maybe it's possible to update only opcodes...

[waddlesplash]

We're on 2.24 ATM. This has long since been fixed.

[pulkomandy]

We are not on 2.24 for gcc2...

[waddlesplash]

Oh, I see. My bad.

[cocobean]

Reviewed on hrev 51986 x86 - (gcc 2.95.3_2017-07-20, objdump 2013-04-21). We can close this ticket.

Easier for FOSS/Haiku devs to open a another terminal, setarch x86, and use the objdump 2.26.1 version.

NOTE: The reporter mentioned: "Update to newer binutils recommended." 10 years ago in which binutils 2.26.1 now available on Haiku. Haiku's binutils 2.17_gcc2 disassembler remains inaccurate on 'several' x86 processor opcodes so best to just use the included binutils 2.26.1_gcc7 disassembler as it seems more stable and accurate at this time. I created a patch to fix the objdump 2.17 issue, yet felt we need to move on. This helps current devs/testers focus on recent binutils 2.29/2.30 testing and deployment.

Technically, we can also use gdb and even: ​https://onlinedisassembler.com

[pulkomandy]

Well, it doesn't seem to be that annoying since one can always use a more recent version of objdump now, in case they hit a similar problem.