This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: objdump -d -r doesn't always show reloc symbol
- From: Andreas Schwab <schwab at suse dot de>
- To: Richard Kennedy <richard at rsk dot demon dot co dot uk>
- Cc: binutils at sourceware dot org
- Date: Sun, 05 Oct 2008 14:43:46 +0200
- Subject: Re: objdump -d -r doesn't always show reloc symbol
- References: <1223209501.2998.18.camel@castor.localdomain>
Richard Kennedy <richard@rsk.demon.co.uk> writes:
> Hi,
> I've been seeing an issue on linux x86_64 when running objdump -d -r on
> some kernel modules.
>
> Occasionally some of the relocated symbols don't get resolved.
What do you mean with "resolved"? objdump just uses the symbol that is
recorded with the relocation info and does not interpret it in any way.
> e.g
> objdump -d -r sound/drivers/snd-dummy.ko
>
> most of it is as expected, except this :-
>
> Disassembly of section .exit.text:
> 0000000000000000 <cleanup_module>:
> 0: e9 00 00 00 00 jmpq 5 <snd_card_dummy_pcm_pointer+0x5>
> 1: R_X86_64_PC32 .text+0x4e
> but I expected to see
> 1: R_X86_64_PC32 snd_dummy_unregister_all-0x04
That would be a different relocation.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."