objdump --full-contents truncates addresses to long

[Alexandre Oliva]

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?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: objdump-64bit-addr.patch
Type: text/x-patch
Size: 797 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/binutils/attachments/20030325/6c2a5017/attachment.bin>
-------------- next part --------------

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer