Opened 17 years ago
Closed 5 years ago
#1768 closed bug (no change required)
Binutils 2.17 objdump Broken
| Reported by: | bonefish | Owned by: | bonefish |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Build System | Version: | R1/Development |
| Keywords: | Cc: | zooey | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
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.
Change History (7)
comment:1 by , 17 years ago
comment:2 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
We're on 2.24 ATM. This has long since been fixed.
comment:4 by , 10 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
| Version: | R1/pre-alpha1 → R1/Development |
Oh, I see. My bad.
comment:6 by , 7 years ago
Did we want to still create a objdump patch for Binutils 2.17 ?
comment:7 by , 5 years ago
| Resolution: | → no change required |
|---|---|
| Status: | reopened → closed |
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.
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...