This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: objdump --full-contents truncates addresses to long
- From: Ian Lance Taylor <ian at airs dot com>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: binutils at sources dot redhat dot com
- Date: 25 Mar 2003 09:24:10 -0800
- Subject: Re: objdump --full-contents truncates addresses to long
- References: <orfzpcapxl.fsf@free.redhat.lsd.ic.unicamp.br>
Alexandre Oliva <aoliva at redhat dot com> writes:
> Truncating to long is not a good idea for a 32-x-64 objdump. Is there
> any reason for us to not use bfd_printf_vma? Perhaps bfd_printf_vma
> should be made more flexible, accepting arguments specifying the a
> minimum/maximum width to be printed, and whether to pad with zeros?
> Other than the ugly implications of this change to the testsuite, that
> I'll look into addressing if this patch is approved, is this ok to
> install along with the testsuite fixes?
Doesn't this make the output particularly ugly when dumping object
files? Perhaps the code could use bfd_sprintf_vma and strip off
excess leading zeroes, while retaining even spacing?
Ian