Bug 2352961

Summary: [abrt] gdb-headless: handle_fatal_signal(): gdb killed by SIGABRT
Product: [Fedora] Fedora Reporter: Joshua <jamal_ali1989>
Component: gdbAssignee: Alexandra Petlanová Hájková <ahajkova>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 41CC: ahajkova, amerey, fweimer, guinevere, jamal_ali1989, jan, keiths, kevinb, mcermak, mkolar, suraj.ghimire7
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/af94391b57af435be6e98e0f7f199929b0924a4
Whiteboard: abrt_hash:773492aa03307a43a275619dc371bc3ff138eb3d;VARIANT_ID=kde;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-04-22 11:17:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: os_info
none
File: proc_pid_status
none
File: open_fds
none
File: environ
none
File: maps
none
File: backtrace
none
File: core_backtrace
none
File: dso_list
none
File: cpuinfo
none
File: mountinfo
none
File: limits none

Description Joshua 2025-03-17 16:21:06 UTC 
Version-Release number of selected component:
gdb-headless-16.2-1.fc43

Additional info:
reporter:       libreport-2.17.15
crash_function: handle_fatal_signal
backtrace_rating: 4
runlevel:       N 5
rootdir:        /
journald_cursor: s=3b4272de1da944d5bf7306dd1a29007c;i=315353e;b=edde515d4bfe4d44920db777aa9e0c2e;m=ca90880a7;t=6307e595831de;x=3b877be88e5ce519
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.freedesktop.GnomeAbrt
type:           CCpp
uid:            1000
package:        gdb-headless-16.2-1.fc43
cmdline:        /usr/libexec/gdb -batch -ex $'set debuginfod enabled on' "" -ex $'file /usr/bin/plasma-discover' -ex $'core-file ./coredump' -ex $'thread apply all -ascending backtrace full 1024' -ex $'info sharedlib' -ex $'print (char*)__abort_msg' -ex $'print (char*)__glib_assert_msg' -ex $'info all-registers' -ex disassemble
kernel:         6.13.5-200.fc41.x86_64
executable:     /usr/libexec/gdb
reason:         gdb killed by SIGABRT

Truncated backtrace:
Thread no. 1 (32 frames)
 #3 handle_fatal_signal at ../../gdb/event-top.c:1039
 #5 __syscall_cancel_arch at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
 #6 __internal_syscall_cancel at cancellation.c:49
 #7 __syscall_cancel at cancellation.c:75
 #8 __poll at ../sysdeps/unix/sysv/linux/poll.c:29
 #9 poll at /usr/include/bits/poll2.h:44
 #10 Curl_poll at ../../lib/select.c:313
 #11 multi_wait at ../../lib/multi.c:1387
 #13 curl_multi_wait at ../../lib/multi.c:1520
 #14 perform_queries at /usr/src/debug/elfutils-0.192-9.fc41.x86_64/debuginfod/debuginfod-client.c:1065
 #15 debuginfod_query_server_by_buildid at /usr/src/debug/elfutils-0.192-9.fc41.x86_64/debuginfod/debuginfod-client.c:2183
 #16 debuginfod_debuginfo_query at ../../gdb/debuginfod-support.c:379
 #17 debuginfod_find_and_open_separate_symbol_file at ../../gdb/symfile-debug.c:557
 #18 objfile::find_and_add_separate_symbol_file at ../../gdb/symfile-debug.c:614
 #19 elf_symfile_read_dwarf2 at ../../gdb/elfread.c:1218
 #20 elf_symfile_read at ../../gdb/elfread.c:1438
 #21 read_symbols at ../../gdb/symfile.c:763
 #22 syms_from_objfile_1 at ../../gdb/symfile.c:962
 #23 syms_from_objfile at ../../gdb/symfile.c:979
 #24 symbol_file_add_with_addrs at ../../gdb/symfile.c:1084
 #25 symbol_file_add_from_bfd at ../../gdb/symfile.c:1158
 #26 solib_read_symbols at ../../gdb/solib.c:651
 #27 solib_add at ../../gdb/solib.c:980
 #28 post_create_inferior at ../../gdb/infcmd.c:291
 #29 core_target_open at ../../gdb/corelow.c:1154
 #30 cmd_func at ../../gdb/cli/cli-decode.c:2748
 #31 execute_command at ../../gdb/top.c:570
 #32 catch_command_errors at ../../gdb/main.c:508
 #33 execute_cmdargs at ../../gdb/main.c:607
 #34 captured_main_1 at ../../gdb/main.c:1308
 #35 captured_main at ../../gdb/main.c:1333
 #36 gdb_main at ../../gdb/main.c:1362
Comment 1 Joshua 2025-03-17 16:21:10 UTC 
Created attachment 2080589 [details]
File: os_info
Comment 2 Joshua 2025-03-17 16:21:12 UTC 
Created attachment 2080590 [details]
File: proc_pid_status
Comment 3 Joshua 2025-03-17 16:21:14 UTC 
Created attachment 2080591 [details]
File: open_fds
Comment 4 Joshua 2025-03-17 16:21:15 UTC 
Created attachment 2080592 [details]
File: environ
Comment 5 Joshua 2025-03-17 16:21:17 UTC 
Created attachment 2080593 [details]
File: maps
Comment 6 Joshua 2025-03-17 16:21:19 UTC 
Created attachment 2080594 [details]
File: backtrace
Comment 7 Joshua 2025-03-17 16:21:21 UTC 
Created attachment 2080595 [details]
File: core_backtrace
Comment 8 Joshua 2025-03-17 16:21:23 UTC 
Created attachment 2080596 [details]
File: dso_list
Comment 9 Joshua 2025-03-17 16:21:24 UTC 
Created attachment 2080597 [details]
File: cpuinfo
Comment 10 Joshua 2025-03-17 16:21:26 UTC 
Created attachment 2080599 [details]
File: mountinfo
Comment 11 Joshua 2025-03-17 16:21:28 UTC 
Created attachment 2080600 [details]
File: limits
Comment 12 Alexandra Petlanová Hájková 2025-03-21 14:31:26 UTC 
Hi Joshua,

is it possible to provide us with the coredump for the issue?

Thank you,
Alexandra
Comment 13 Joshua 2025-03-22 18:21:28 UTC 
(In reply to Alexandra Petlanová Hájková from comment #12)
> Hi Joshua,
> 
> is it possible to provide us with the coredump for the issue?
> 
> Thank you,
> Alexandra

Dear Alexandra,

Unfortunately, I had an issue with my "Problem reporting" tool and I had to reinstall it, so all the previous reports are gone. However, I do recall choosing all the available entries before reporting this crash.
On the other hand, a very similar crash appeared a few hours ago and I reported it here: https://bugzilla.redhat.com/show_bug.cgi?id=2325177

If it helps, I can send the coredump for that crash. I just need the instructions on how to provide it.

Best regards,
Joshua
Comment 14 Alexandra Petlanová Hájková 2025-03-24 10:07:09 UTC 
(In reply to Joshua from comment #13)

> Dear Alexandra,
> 
> Unfortunately, I had an issue with my "Problem reporting" tool and I had to
> reinstall it, so all the previous reports are gone. However, I do recall
> choosing all the available entries before reporting this crash.
> On the other hand, a very similar crash appeared a few hours ago and I
> reported it here: https://bugzilla.redhat.com/show_bug.cgi?id=2325177
> 
> If it helps, I can send the coredump for that crash. I just need the
> instructions on how to provide it.
> 
> Best regards,
> Joshua


Hi Joshua,

it's the best when you can provide the reproducer, but the coredump is next the 
most helpful thing when debugging these issues. Please, provide the coredump
whenever it's possible for you. The best way how to provide it is attaching it
to the bug like the other logs.

Thank you,
Alexandra
Comment 15 Joshua 2025-03-25 07:37:01 UTC 
Dear Alexandra,

If I submit a bug with the "Problem reporting" tool and check every option, would that include the coredump as well?

Regards,
Joshua
Comment 16 Alexandra Petlanová Hájková 2025-03-26 16:09:57 UTC 
(In reply to Joshua from comment #15)
> Dear Alexandra,
> 
> If I submit a bug with the "Problem reporting" tool and check every option,
> would that include the coredump as well?
> 
> Regards,
> Joshua

The tool doesn't add corefiles because they are big and can reveal personal information from a system so you have to add the coredump manually if you decide it's ok to share it.
Comment 17 Joshua 2025-03-27 17:51:22 UTC 
(In reply to Alexandra Petlanová Hájková from comment #16)
> (In reply to Joshua from comment #15)
> > Dear Alexandra,
> > 
> > If I submit a bug with the "Problem reporting" tool and check every option,
> > would that include the coredump as well?
> > 
> > Regards,
> > Joshua
> 
> The tool doesn't add corefiles because they are big and can reveal personal
> information from a system so you have to add the coredump manually if you
> decide it's ok to share it.

Dear Alexandra,

In that case, please refer me to an up-to-date source on how to locate coredump files for such errors. I'll make sure to include them when necessary.
Comment 18 Alexandra Petlanová Hájková 2025-04-07 09:27:37 UTC 
(In reply to Joshua from comment #17)
> (In reply to Alexandra Petlanová Hájková from comment #16)
> > (In reply to Joshua from comment #15)
> > > Dear Alexandra,
> > > 
> > > If I submit a bug with the "Problem reporting" tool and check every option,
> > > would that include the coredump as well?
> > > 
> > > Regards,
> > > Joshua
> > 
> > The tool doesn't add corefiles because they are big and can reveal personal
> > information from a system so you have to add the coredump manually if you
> > decide it's ok to share it.
> 
> Dear Alexandra,
> 
> In that case, please refer me to an up-to-date source on how to locate
> coredump files for such errors. I'll make sure to include them when
> necessary.

There's a gnome-abrt command to look for core dumps using the GUI for RHEL 7 or 8,
ABRT is not present in RHEL 9, The Coredumps can be captured through systemd coredumpctl functionality.

You can find more detials in this article: https://access.redhat.com/solutions/56021

I hope it's hepful,
Alexandra