[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/26087] objdump --reloc does not work
From: |
nickc at redhat dot com |
Subject: |
[Bug binutils/26087] objdump --reloc does not work |
Date: |
Mon, 08 Jun 2020 10:29:25 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=26087
Nick Clifton <nickc at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nickc at redhat dot com
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Nick Clifton <nickc at redhat dot com> ---
Hi Martin,
This is due to a difference in the behaviour of readelf and objdump.
With readelf with --relocs option will dump both static relocs and
dynamic relocs. With objdump the --reloc option will *only* dump
static relocs. If you want to see the dynamic relocs you need to
use the --dynamic-reloc option. Vis:
$ objdump --dynamic-reloc relocoverwrite
/home/nickc/Downloads/relocoverwrite: file format elf64-x86-64
DYNAMIC RELOCATION RECORDS
OFFSET TYPE VALUE
0000000000003de0 R_X86_64_RELATIVE *ABS*+0x0000000000001240
0000000000003de8 R_X86_64_RELATIVE *ABS*+0x00000000000011f0
0000000000004048 R_X86_64_RELATIVE *ABS*+0x0000000000004048
0000000000003fd0 R_X86_64_GLOB_DAT _ITM_deregisterTMCloneTable
0000000000003fd8 R_X86_64_GLOB_DAT printf@GLIBC_2.2.5
0000000000003fe0 R_X86_64_GLOB_DAT __libc_start_main@GLIBC_2.2.5
0000000000003fe8 R_X86_64_GLOB_DAT __gmon_start__
0000000000003ff0 R_X86_64_GLOB_DAT _ITM_registerTMCloneTable
0000000000003ff8 R_X86_64_GLOB_DAT __cxa_finalize@GLIBC_2.2.5
0000000000004050 R_X86_64_COPY stdout@@GLIBC_2.2.5
0000000000004060 R_X86_64_COPY stdin@@GLIBC_2.2.5
0000000000004018 R_X86_64_JUMP_SLOT puts@GLIBC_2.2.5
0000000000004020 R_X86_64_JUMP_SLOT __stack_chk_fail@GLIBC_2.4
0000000000004028 R_X86_64_JUMP_SLOT read@GLIBC_2.2.5
0000000000004030 R_X86_64_JUMP_SLOT setvbuf@GLIBC_2.2.5
0000000000004038 R_X86_64_JUMP_SLOT __isoc99_scanf@GLIBC_2.7
Cheers
Nick
--
You are receiving this mail because:
You are on the CC list for the bug.