This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: objdump : Odd formating if disassembly with --enable-64-bit-bfd
- To: Erik de Castro Lopo <nospam at mega-nerd dot com>
- Subject: Re: objdump : Odd formating if disassembly with --enable-64-bit-bfd
- From: Alan Modra <alan at linuxcare dot com dot au>
- Date: Fri, 12 Jan 2001 10:55:37 +1100 (EST)
- cc: binutils at sourceware dot cygnus dot com
On Thu, 11 Jan 2001, Erik de Castro Lopo wrote:
> No, I've got no complaints about that. The thing I think is odd is that
> the movl does not line up with the call and push instructions. This makes
> the aseembly listing much more difficult to read.
>
> 0x0000000008049325 68 b1 f0 04 08 push $0x804f0b1
> 0x000000000804932a e8 75 fc ff ff call 0x0000000008048fa4
> 0x000000000804932f c7 05 34 2c 05 08 00 00 00 00 movl $0x0,0x8052c34
Hmm, that seems to be a side-effect of turning on prefix-intructions.
objdump.c:disassemble_bytes around line 1410 has:
/* If ! prefix_addresses and ! wide_output, we print
octets_per_line octets per line. */
pb = octets;
if (pb > octets_per_line && ! prefix_addresses && ! wide_output)
pb = octets_per_line;
You could remove `&& ! prefix_addresses' here, but that results in output
like the following
0x0000000008049347 c7 05 7c 47 05 08 00 movl $0x0,0x805477c
804934e: 00 00 00
which is probably why the condition was added. Feel free to provide
patches to fix the problem ;-)
--
Linuxcare. Support for the Revolution.