Re: Possible bug in binutils: objdump

[Hans-Bernhard Broeker]

Sean Watkinson <address@hidden> wrote:
> I am currently running version 2.10.90 of objdump from the binutils
> distribution to disassemble an old MS-DOS executable of mine. I'd
> stripped away the MZEXE header and performed the following:

>      objdump -D -m i8086 -b binary stripped.exe

> one line in the resulting code reads:

>      1878c: e8 87 f5              call   0x7d16

IMHO the output is quite fine as it is.

Note that we're talking about 8086 code here, which cannot possibly
ever have an IP of 1878c in the first place anyway.  That's beyond the
64K address range size barrier.  IIRC an 8086 if requested by a
relative jump to reach beyond a 64K barrier *will* wrap around to the
beginning of the same 64K segment, i.e.

        ff00: e8 00 02   (call relative +0200))

will actually be a "call 0103", not a "call 10103".

The bug, if any, is that the disassembly didn't stop dead in its track
as soon as it found a binary image of more than 64K in size, and print
an error message.
-- 
Hans-Bernhard Broeker (address@hidden)
Even if all the snow were burnt, ashes would remain.