https://sourceware.org/bugzilla/show_bug.cgi?id=26087
Bug ID: 26087 Summary: objdump --reloc does not work Product: binutils Version: 2.34 Status: UNCONFIRMED Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: martin at dev2day dot de Target Milestone: --- Created attachment 12594 --> https://sourceware.org/bugzilla/attachment.cgi?id=12594&action=edit file that I used to run objdump and readelf as described in the Description field Hello! When running obdjump on the attached file I get the following (empty) output: $ objdump --reloc relocoverwrite relocoverwrite: file format elf64-x86-64 When I run readelf I get the following output: $ readelf --relocs relocoverwrite Relocation section '.rela.dyn' at offset 0x5c0 contains 11 entries: Offset Info Type Sym. Value Sym. Name + Addend 000000003de0 000000000008 R_X86_64_RELATIVE 1240 000000003de8 000000000008 R_X86_64_RELATIVE 11f0 000000004048 000000000008 R_X86_64_RELATIVE 4048 000000003fd0 000100000006 R_X86_64_GLOB_DAT 0000000000000000 _ITM_deregisterTMClone + 0 000000003fd8 000d00000006 R_X86_64_GLOB_DAT 0000000000000000 printf@GLIBC_2.2.5 + 0 000000003fe0 000500000006 R_X86_64_GLOB_DAT 0000000000000000 __libc_start_main@GLIBC_2.2.5 + 0 000000003fe8 000600000006 R_X86_64_GLOB_DAT 0000000000000000 __gmon_start__ + 0 000000003ff0 000900000006 R_X86_64_GLOB_DAT 0000000000000000 _ITM_registerTMCloneTa + 0 000000003ff8 000a00000006 R_X86_64_GLOB_DAT 0000000000000000 __cxa_finalize@GLIBC_2.2.5 + 0 000000004050 000b00000005 R_X86_64_COPY 0000000000004050 stdout@GLIBC_2.2.5 + 0 000000004060 000c00000005 R_X86_64_COPY 0000000000004060 stdin@GLIBC_2.2.5 + 0 Relocation section '.rela.plt' at offset 0x6c8 contains 5 entries: Offset Info Type Sym. Value Sym. Name + Addend 000000004018 000200000007 R_X86_64_JUMP_SLO 0000000000000000 puts@GLIBC_2.2.5 + 0 000000004020 000300000007 R_X86_64_JUMP_SLO 0000000000000000 __stack_chk_fail@GLIBC_2.4 + 0 000000004028 000400000007 R_X86_64_JUMP_SLO 0000000000000000 read@GLIBC_2.2.5 + 0 000000004030 000700000007 R_X86_64_JUMP_SLO 0000000000000000 setvbuf@GLIBC_2.2.5 + 0 000000004038 000800000007 R_X86_64_JUMP_SLO 0000000000000000 __isoc99_scanf@GLIBC_2.7 + 0 It seems that objdump is not able to read the relocation entries. I tested this on Ubuntu 20.04 and Fedora 32. Same behavior. Best Martin -- You are receiving this mail because: You are on the CC list for the bug.