Install mutt and its debuginfo, and the objdump disassembler cannot use debuginfo: $ objdump -d --reloc /usr/bin/mutt | grep -w 'ea030:' -B 5 -A 10 ea01c: 0f 1f 40 00 nopl 0x0(%rax) ea020: e8 3b a6 fe ff callq d4660 <sasl_client_new@plt+0xbc720> ea025: eb 87 jmp e9fae <sasl_client_new@plt+0xd206e> ea027: e8 84 d4 f2 ff callq 174b0 <__stack_chk_fail@plt> ea02c: 0f 1f 40 00 nopl 0x0(%rax) ea030: f3 0f 1e fa endbr64 ea034: 41 55 push %r13 ea036: 41 54 push %r12 ea038: 55 push %rbp ea039: 53 push %rbx ea03a: 48 83 ec 18 sub $0x18,%rsp ea03e: 64 48 8b 04 25 28 00 mov %fs:0x28,%rax ea045: 00 00 ea047: 48 89 44 24 08 mov %rax,0x8(%rsp) ea04c: 31 c0 xor %eax,%eax ea04e: 80 3a 2a cmpb $0x2a,(%rdx) GDB can pick it up: $ gdb /usr/bin/mutt […] (gdb) disassemble 0xea030 Dump of assembler code for function msg_fetch_header.isra.0: 0x00000000000ea030 <+0>: endbr64 0x00000000000ea034 <+4>: push %r13 0x00000000000ea036 <+6>: push %r12 0x00000000000ea038 <+8>: push %rbp 0x00000000000ea039 <+9>: push %rbx 0x00000000000ea03a <+10>: sub $0x18,%rsp 0x00000000000ea03e <+14>: mov %fs:0x28,%rax 0x00000000000ea047 <+23>: mov %rax,0x8(%rsp) 0x00000000000ea04c <+28>: xor %eax,%eax 0x00000000000ea04e <+30>: cmpb $0x2a,(%rdx) 0x00000000000ea051 <+33>: jne 0xea180 <msg_fetch_header.isra.0+336> 0x00000000000ea057 <+39>: mov %rdi,%r12 0x00000000000ea05a <+42>: mov %rdx,%rdi 0x00000000000ea05d <+45>: mov %rsi,%rbx 0x00000000000ea060 <+48>: mov %rcx,%rbp 0x00000000000ea063 <+51>: call 0xd58f0 <imap_next_word> […] Seen with: binutils-2.35-18.fc33.x86_64 mutt-1.14.6-2.fc33.x86_64 mutt-debuginfo-1.14.6-2.fc33.x86_64
Try objdump -d --dwarf=follow-links --reloc /usr/bin/mutt
Ugh, thanks. Can we make this the default, at least if we hard-code some trusted paths?
(In reply to Florian Weimer from comment #2) > Ugh, thanks. Can we make this the default, The upstream binutils development sources now default to enabling link following unless a configure option is used to change this. > at least if we hard-code some trusted paths? At the moment all paths are trusted. I am not sure of the security implications for this, but I believe that it is how all of the debug link following tools currently behave.
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.