Description of problem: Happens every time I compile scummvm. Version-Release number of selected component: binutils-2.39-9.fc38 Additional info: reporter: libreport-2.17.9 cmdline: dwp -e ./scummvm-conf -o /dev/null type: CCpp cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-kitty-3838.scope runlevel: N 5 package: binutils-2.39-9.fc38 journald_cursor: s=4b4e9570774c43efacdbf61ff62ab96f;i=54f5d;b=3473737d77ab48b0ace91e72c2f674ac;m=1be6bb552;t=5fa816aa0fec4;x=f28b2ad6d22bfb3d executable: /usr/bin/dwp rootdir: / kernel: 6.2.12-300.fc38.x86_64 reason: dwp killed by SIGSEGV backtrace_rating: 4 comment: Happens every time I compile scummvm. crash_function: fseek uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 fseek at fseek.c:35 #1 gold::Dwp_output_file::write_new_section at /usr/src/debug/binutils-2.39-9.fc38.x86_64/gold/dwp.cc:1961 #2 gold::Dwp_output_file::write_index<false> at /usr/src/debug/binutils-2.39-9.fc38.x86_64/gold/dwp.cc:2070 #3 gold::Dwp_output_file::finalize at /usr/src/debug/binutils-2.39-9.fc38.x86_64/gold/dwp.cc:1874 Potential duplicate: bug 2136183
Created attachment 1961228 [details] File: maps
Created attachment 1961229 [details] File: exploitable
Created attachment 1961230 [details] File: open_fds
Created attachment 1961231 [details] File: environ
Created attachment 1961232 [details] File: dso_list
Created attachment 1961233 [details] File: cpuinfo
Created attachment 1961234 [details] File: limits
Created attachment 1961235 [details] File: os_info
Created attachment 1961236 [details] File: proc_pid_status
Created attachment 1961237 [details] File: backtrace
Created attachment 1961238 [details] File: core_backtrace
Created attachment 1961239 [details] File: mountinfo
This looks another instance of this upstream bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=15447 As a workaround you could probably just skip the invocation of dwp during the build of scummvm. In the meantime, I will test the patch from the upstream PR.
Fixed in binutils-2.40-8.fc39, binutils-2.39-12.fc38 and binutils-2.38-27.fc37
FEDORA-2023-fb366d5ed5 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-fb366d5ed5
FEDORA-2023-14607e274c has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-14607e274c
FEDORA-2023-eafe3fad16 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-eafe3fad16
FEDORA-2023-fb366d5ed5 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-fb366d5ed5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-fb366d5ed5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-eafe3fad16 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-eafe3fad16` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-eafe3fad16 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-14607e274c has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-14607e274c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-14607e274c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-14607e274c has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-fb366d5ed5 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.