Fedora Account System
Red Hat Associate
Red Hat Customer
gdb --version GNU gdb (Fedora Linux) 17.2-1.fc44 gdb seems to run quite often into an intern error. Can be reproduced most of the time in a VM updated to 2026-07-08 I suspect that this might happen only with multi-threaded programs reproducer with audacious Reproducible: Sometimes Steps to Reproduce: I would say reproducibility is most of the time ( 8-9 out of 10 ) 1.start audacious and play an audio stream e.g https://listen-ssvcbfbs.sharp-stream.com/ssvcbfbs22.aac ( works probably w/o active audio stream ) 2. pkill --signal 11 audacious 3. coredumpctl list might show two new entries for audacious and for gdb(!) 4. coredumpctl debug <pid_audacious> to provoke the interal error Actual Results: internal gdb error , session terminates and creates two(!) new entries in coredumpctl list Expected Results: get to the (gdb) prompt to enter gdb command like "bt full" Additional Information: I'll attach output of a kvm session, 2nd try forced the error and got the backtrace backtrace --- Fatal signal: Segmentation fault ----- Backtrace ----- 0x55dfc36c9191 gdb_internal_backtrace_1 ../../gdb/bt-utils.c:122 0x55dfc36c9191 _Z22gdb_internal_backtracev ../../gdb/bt-utils.c:175 0x55dfc3820f06 handle_fatal_signal ../../gdb/event-top.c:1013 0x55dfc382112e handle_sigsegv ../../gdb/event-top.c:1090 0x7f6b952210af ??? 0x55dfc37454df _ZN16core_mapped_file6regionC4Emmm ../../gdb/gdbcore.h:272 0x55dfc37454df _ZSt12construct_atIN16core_mapped_file6regionEJRmS2_S2_EQaant20is_unbounded_array_vIT_ErqXgsnwcvPvLi0E_S3_pispcl7declvalIT0_EEEEEPS3_S6_DpOS5_ /usr/include/c++/16/bits/stl_construct.h:110 0x55dfc37454df _ZNSt16allocator_traitsISaIN16core_mapped_file6regionEEE9constructIS1_JRmS5_S5_EEEvRS2_PT_DpOT0_ /usr/include/c++/16/bits/alloc_traits.h:716 0x55dfc37454df _ZNSt6vectorIN16core_mapped_file6regionESaIS1_EE12emplace_backIJRmS5_S5_EEERS1_DpOT_ /usr/include/c++/16/bits/vector.tcc:121 0x55dfc37454df operator() ../../gdb/corelow.c:2157 0x55dfc37454df operator() ../../gdb/../gdbsupport/function-view.h:305 0x55dfc37454df _FUN ../../gdb/../gdbsupport/function-view.h:299 0x55dfc3901849 _ZNK3gdb13function_viewIFvimmmPKcPK12bfd_build_idEEclEimmmS2_S5_ ../../gdb/../gdbsupport/function-view.h:289 0x55dfc3901849 linux_read_core_file_mappings ../../gdb/linux-tdep.c:1237 0x55dfc373e06e _Z27gdb_read_core_file_mappingsP7gdbarchP3bfd ../../gdb/corelow.c:2120 0x55dfc3740f10 _ZN11core_target19build_file_mappingsEv ../../gdb/corelow.c:375 0x55dfc374234b _ZN11core_targetC2Ev ../../gdb/corelow.c:350 0x55dfc3742541 core_target_open ../../gdb/corelow.c:1020 0x55dfc391c809 catch_command_errors ../../gdb/main.c:511 0x55dfc391f27a captured_main_1 ../../gdb/main.c:1256 0x55dfc3920b01 captured_main ../../gdb/main.c:1349 0x55dfc3920b01 _Z8gdb_mainP18captured_main_args ../../gdb/main.c:1378 0x55dfc35a3f5d main ../../gdb/gdb.c:38 --------------------- A fatal error internal to GDB has been detected, further debugging is not possible. GDB will now terminate.
Created attachment 2148020 [details] output kvm session
To fix this we need to backport upstream commit: commit 93f536d813c41527e8c939a5f8a90a4b37a5abab Date: Mon Oct 13 15:11:09 2025 +0100 gdb/corelow: Fix use-after-free in gdb_read_core_file_mappings We can probably do this once the 17.2 rebase is complete.
Sorry, I'm having a slow day. I realise this is against 17.2. I'll get the fix backported tomorrow.
*** Bug 2498770 has been marked as a duplicate of this bug. ***
Fixes have been merged: https://src.fedoraproject.org/rpms/gdb/pull-request/222 https://src.fedoraproject.org/rpms/gdb/pull-request/223 https://src.fedoraproject.org/rpms/gdb/pull-request/224
*** Bug 2498425 has been marked as a duplicate of this bug. ***
*** Bug 2499552 has been marked as a duplicate of this bug. ***
*** Bug 2499364 has been marked as a duplicate of this bug. ***
FEDORA-2026-3a8f9747f8 (gdb-17.2-2.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-3a8f9747f8
FEDORA-2026-2c86563178 (gdb-17.2-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-2c86563178
FEDORA-2026-2c86563178 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-2c86563178` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-2c86563178 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-3a8f9747f8 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-3a8f9747f8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-3a8f9747f8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-2c86563178 (gdb-17.2-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-3a8f9747f8 (gdb-17.2-2.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
*** Bug 2500776 has been marked as a duplicate of this bug. ***
*** Bug 2500797 has been marked as a duplicate of this bug. ***