This is the mail archive of the
mailing list for the binutils project.
[SH] 0x on hex numbers in disassembly
- From: Andrew STUBBS <andrew dot stubbs at st dot com>
- To: binutils at sourceware dot org
- Date: Fri, 20 Oct 2006 13:06:25 +0100
- Subject: [SH] 0x on hex numbers in disassembly
80019d0: 15 d1 mov.l 8001a28 <_main+0x68>,r1 ! 0x800c28c
0x080019d0 <main+16>: mov.l 0x8001a28 <main+104>,r1 ! 0x0x800c28c
Spot the 0x differences. GDB always prints addresses with 0x, binutils
always prints them without.
Or that's how it's supposed to be (I don't know why). The observant will
have noticed that binutils gives 0x in the comment, while gdb gives TWO.
This is because whoever wrote the sh-dis.c thought that there ought to
be 0x in those places.
The problem is that GDB prints its own 0x and so we get two. Actually
the real problem is that I can't figure out how to get rid of the second
one without changing the binutils output.
Would anybody mind if binutils stop giving 0x on these addresses?