Fedora Account System
Red Hat Associate
Red Hat Customer
Version-Release number of selected component: gdb-headless-16.3-6.fc43 Additional info: reporter: libreport-2.17.15 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.qt\x2dproject.qtcreator-3562.scope rootdir: / runlevel: /bin/sh: line 1: runlevel: command not found uid: 1000 reason: gdb killed by SIGABRT package: gdb-headless-16.3-6.fc43 executable: /usr/libexec/gdb crash_function: dump_core cmdline: /usr/bin/gdb --tty=/tmp/QtCreator-fYqaza/outputcollector.bJbggO -i mi journald_cursor: s=da6a85cce61f483f880c5430041cd107;i=c7fdf;b=27297b6e077e45f894ca7a00af39ad7f;m=70817c9a;t=6434dc8e8cf5f;x=f6edb688a3a1e669 type: CCpp kernel: 6.17.7-300.fc43.x86_64 Truncated backtrace: Thread no. 1 (20 frames) #4 dump_core at ../../gdb/utils.c:225 #5 internal_vproblem(internal_problem *, const char *, int, const char *, typedef __va_list_tag __va_list_tag *) at ../../gdb/utils.c:477 #6 internal_verror at ../../gdb/utils.c:503 #7 internal_error_loc at ../../gdbsupport/errors.cc:57 #8 report_exit_events_for at ../../gdb/linux-nat.c:331 #10 linux_nat_filter_event at ../../gdb/linux-nat.c:3063 #11 linux_nat_wait_1 at ../../gdb/linux-nat.c:3377 #12 linux_nat_target::wait at ../../gdb/linux-nat.c:3603 #13 thread_db_target::wait at ../../gdb/linux-thread-db.c:1401 #14 target_wait at ../../gdb/target.c:2582 #15 do_target_wait_1 at ../../gdb/infrun.c:4144 #16 operator() at ../../gdb/infrun.c:4206 #17 do_target_wait at ../../gdb/infrun.c:4225 #18 fetch_inferior_event at ../../gdb/infrun.c:4666 #19 gdb_wait_for_event at ../../gdbsupport/event-loop.cc:694 #20 gdb_do_one_event at ../../gdbsupport/event-loop.cc:216 #21 start_event_loop at ../../gdb/main.c:402 #22 captured_command_loop at ../../gdb/main.c:466 #23 captured_main at ../../gdb/main.c:1343 #24 gdb_main at ../../gdb/main.c:1362 Potential duplicate: bug 1419703
Created attachment 2113845 [details] File: limits
Created attachment 2113846 [details] File: backtrace
Created attachment 2113847 [details] File: os_info
Created attachment 2113848 [details] File: environ
Created attachment 2113849 [details] File: maps
Created attachment 2113850 [details] File: open_fds
Created attachment 2113851 [details] File: cpuinfo
Created attachment 2113852 [details] File: core_backtrace
Created attachment 2113853 [details] File: mountinfo
Created attachment 2113854 [details] File: dso_list
Created attachment 2113855 [details] File: proc_pid_status
Can you upload the core file associated with the crash when running qtcreator ? To find it, look at the output from running "abrt-cli", then do "abrt-cli info ID" where ID is the hex identifier (left-most field) obtained from looking at the abrt-cli output. Output from the "abrt-cli info" command will show a path (most likely starting with /var/spool/abrt). Look in that directory - you should hopefully see a file named coredump.zst. Upload that file to this bug. Thanks!
This happened after libreport crashed, while trying to submit a bug report for gnome-shell crashing (ID# 2444685). reporter: libreport-2.17.15 type: CCpp reason: gdb killed by SIGABRT journald_cursor: s=96b2d2900428480fbc6aa6ce2306f817;i=1919d;b=9bf18fb57f624d1b96680e612658388d;m=4a9aeca18;t=64c3a20c5f20b;x=4573025f3e6b33b3 executable: /usr/libexec/gdb cmdline: /usr/libexec/gdb -batch -ex $'set debuginfod enabled on' "" -ex $'file /usr/bin/report-gtk' -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 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.freedesktop.problems.applet rootdir: / uid: 1000 kernel: 6.18.13-200.fc43.x86_64 package: gdb-headless-17.1-4.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: dump_core comment: This happened after libreport crashed, while trying to submit a bug report for gnome-shell crashing (ID# 2444685).
Used Heroic Launcher (Flatpack, 2.20.1) to run Cyberpunk 2077 (GOG, latest version) with GE-Proton-latest. When quitting the game it took a while for the process to end. After a few seconds I got the notification that wine64-preloader had crashed. When I tried to generate a report for that crash, gdb crashed after a while and this report got generated. reporter: libreport-2.17.15 type: CCpp reason: gdb killed by SIGABRT journald_cursor: s=8b8c43cc69bb45c0a487f9f0d3ff41f1;i=451b42;b=96bf2cb8dd004102a6bf15bf80ff6105;m=3fa6448a;t=64d4a59b9381c;x=4dc5c0bbf2232a49 executable: /usr/libexec/gdb cmdline: /usr/libexec/gdb -batch -ex $'set debuginfod enabled on' "" -ex $'file /home/martin/.local/share/Steam/compatibilitytools.d/GE-Proton-latest/files/bin/wine64-preloader' -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 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.freedesktop.problems.applet rootdir: / uid: 1000 kernel: 6.19.7-200.fc43.x86_64 package: gdb-headless-17.1-4.fc43 runlevel: /bin/sh: Zeile 1: runlevel: Kommando nicht gefunden backtrace_rating: 4 crash_function: dump_core comment: Used Heroic Launcher (Flatpack, 2.20.1) to run Cyberpunk 2077 (GOG, latest version) with GE-Proton-latest. When quitting the game it took a while for the process to end. After a few seconds I got the notification that wine64-preloader had crashed. When I tried to generate a report for that crash, gdb crashed after a while and this report got generated.
I've closed this bug. No core dump was provided for the original bug, which happened to be in gdb-headless-16.3-6.fc43. Since then, ABRT has, for some reason, attached two additional reports to this bug. Both of these are for gdb-headless-17.1-4.fc43. Unfortunately, no backtrace has been provided. While I might guess that it's similar to that of the original bug, I would really prefer to see it for myself. Also, given the fact that these bugs are for entirely different GDB releases, it is possible that the bug for the first problem has been fixed. (I also have some AI analysis which indicates that ABRT's duplicate detection mechanism may be incorrect here.) This bug was closed in hopes that new reports will end up in their own bugs with proper backtraces describing that problem.
Was running abrt to report crashes. reporter: libreport-2.17.15 rootdir: / executable: /usr/libexec/gdb cmdline: /usr/libexec/gdb -batch -ex $'set debuginfod enabled on' "" -ex $'file /usr/lib/jvm/java-21-openjdk/bin/java' -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 cgroup: 0::/user.slice/user-1001.slice/user/app.slice/app-gnome-org.freedesktop.GnomeAbrt-2789240.scope journald_cursor: s=6b102c5b0a334757b3fed410c95192f6;i=21bd112b;b=5d9cfebc60e34dbd9c40bf0211730074;m=eda58b779e;t=64f21bbf31f4a;x=65e301d988172ee4 package: gdb-headless-17.1-4.fc43 uid: 1001 runlevel: /bin/sh: line 1: runlevel: command not found crash_function: dump_core comment: Was running abrt to report crashes. backtrace_rating: 4 type: CCpp kernel: 6.19.9-200.fc43.x86_64 reason: gdb killed by SIGABRT
Created attachment 2136648 [details] Backtrace from abrt > This bug was closed in hopes that new reports will end up in their own bugs with proper backtraces describing that problem. Nope. Seems not. Heres's the backtrace from mine.