This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: RFA: objdump -D on binary files and 64-bit address spaces
- From: Alan Modra <amodra at gmail dot com>
- To: Cary Coutant <ccoutant at google dot com>
- Cc: Binutils <binutils at sourceware dot org>
- Date: Fri, 27 Sep 2013 13:57:15 +0930
- Subject: Re: RFA: objdump -D on binary files and 64-bit address spaces
- Authentication-results: sourceware.org; auth=none
- References: <CAHACq4r=QEDxhgxKQ0WuOq0Oz6-Tm9OheP0rxJLMC2kr-Aqy5Q at mail dot gmail dot com>
On Tue, Sep 24, 2013 at 04:50:05PM -0700, Cary Coutant wrote:
> When running objdump -D on a binary file (say, a dump directly from
> memory of dynamically-generated code), you can use the -m and -M
> options to specify the target architecture, but that's not quite
> enough. If the --adjust-vma option is used to place the dumped code at
> a large (> 2^32) address, objdump still prints addresses truncated to
> 32 bits. For example:
>
> $ objdump -D -b binary -m i386 -M x86-64
> --adjust-vma=0x00007f9fa10747e0 --start-address=0x00007f9fa10c7f90
> --stop-address=0x00007f9fa10c88b0 --no-show-raw dump
Try using -m i386:x86-64
--
Alan Modra
Australia Development Lab, IBM