Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Steps to reproduce: objdump -dSC comet.efi I'll attach the binary Version-Release number of selected component: binutils-2.31.1-17.fc29 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: objdump -dSC target/x86_64-unknown-uefi/debug/comet.efi crash_function: _bfd_dwarf2_find_symbol_bias executable: /usr/bin/objdump journald_cursor: s=496f0454c6fc4de2b5cbe9e190a9b7cf;i=5a3c6;b=926caf6cff4b4d44b728cdaa57a60879;m=9904d51b;t=58360364202b9;x=18a4dad498a1654f kernel: 4.20.11-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _bfd_dwarf2_find_symbol_bias at ./dwarf2.c:4482 #1 coff_find_nearest_line_with_names at coffgen.c:2306 #2 show_line at ./objdump.c:1509 #3 disassemble_bytes at ./objdump.c:1820 #4 disassemble_section at ./objdump.c:2342 #5 bfd_map_over_sections at section.c:1374 #6 disassemble_data at ./objdump.c:2478 #7 dump_bfd at ./objdump.c:3631 #8 display_object_bfd at ./objdump.c:3688 #9 display_any_bfd at ./objdump.c:3777
Created attachment 1541155 [details] File: backtrace
Created attachment 1541156 [details] File: cgroup
Created attachment 1541157 [details] File: core_backtrace
Created attachment 1541158 [details] File: cpuinfo
Created attachment 1541159 [details] File: dso_list
Created attachment 1541160 [details] File: environ
Created attachment 1541161 [details] File: exploitable
Created attachment 1541162 [details] File: limits
Created attachment 1541163 [details] File: maps
Created attachment 1541164 [details] File: mountinfo
Created attachment 1541165 [details] File: open_fds
Created attachment 1541166 [details] File: proc_pid_status
Created attachment 1541168 [details] The file that makes objdump segfault
Hi Julian, Thanks for reporting this bug. I have now updated the binutils rpms so that this issue should be resolved. Cheers Nick Fixed in: binutils-2.31.1-24.fc29, binutils-2.31.1-29.fc30, binutils-2.32-9.fc31
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.