Home Original page

objdump prints PE relocations with --private-headers, not --reloc

Ian Lance Taylor ian@airs.com
Thu Oct 30 20:14:00 GMT 2003 
Nick Clifton <nickc@redhat.com> writes:

> Hi Pavel,
> 
> > My plan was to fix objdump to print relocations as the first step of
> > getting familiar with GNU binutils and the issues involved.
> >
> > Then I found that objdump can already dump PE relocations, it just treats
> > them as "private" information.  So the intent of my question was if there
> > is any fundamental reason for that, or it's something that can and should
> > be fixed.
> 
> 
> Oh right, in which case the answer is "no there is no fundamental
> reason why the relocs have to be displayed as part of the private
> information" and "yes, please do fix this and submit a patch".

Note that relocations in an executable file should not normally be
dumped by objdump -r (--reloc), they should be dumped by objdump -R
(--dynamic-reloc).

Executable file relocation information is not the same as object file
relocation information.  The latter is processed by the program
linker, the former by the dynamic linker.  That's why we have
different options in objdump to dump them.

It would be appropriate for objdump -R to dump dynamic relocations for
PE executables.

Ian
More information about the Binutils mailing list