Here is a Python script that creates a raw binary and runs objdump on it to
reproduce the problem with the output following...
# ========================================================================
import commands
raw_binary = open("raw_binary", "w")
raw_binary.write(chr(0x1f) + chr(0x19) + chr(0x42) + chr(0xc3))
raw_binary.write(chr(0x6d) + chr(0xe8) + chr(0x6e) + chr(0x50))
raw_binary.write(chr(0x17) + chr(0x23) + chr(0xa9) + chr(0xb7))
raw_binary.write(chr(0x77) + chr(0xce) + chr(0x1b) + chr(0xf9))
raw_binary.close()
print commands.getoutput("objdump -D --target=binary -m arm7tdmi raw_binary")
# ========================================================================
% python foo.py
raw_binary: file format binary
Disassembly of section .data:
00000000 <.data>:
0: c342191f cmpgt r2, #507904 ; 0x7c000
4: 506ee86d rsbpl lr, lr, sp, ror #16
8: b7a92317 undefined
c: f91bce77 undefined instruction 0xf91bce77
-----
Notice that the first 2 instructions have a immediate value but only the first
once has a comment with the hex equivalent.
Also, notice the last 2 instructions are both undefined's yet only the last one
repeats the hex representation of the instruction.
--
Summary: inconsistencies in objdump's presentation of undefined's
and comments
Product: binutils
Version: 2.19
Status: NEW
Severity: normal
Priority: P2
Component: binutils
AssignedTo: unassigned at sources dot redhat dot com
ReportedBy: chris at seberino dot org
CC: bug-binutils at gnu dot org
http://sourceware.org/bugzilla/show_bug.cgi?id=10297------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
bug-binutils mailing list
bug-binutils@...
http://lists.gnu.org/mailman/listinfo/bug-binutils
