Description of problem: GDB crashes while trying to generate a stack trace for a problem report for xdg-desktop-portal-gnome Version-Release number of selected component: gdb-headless-13.1-1.fc38 Additional info: reporter: libreport-2.17.8 reason: gdb killed by SIGSEGV cmdline: /usr/libexec/gdb -batch -ex $'set debuginfod enabled on' "" -ex $'file /usr/libexec/gdb' -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 rootdir: / uid: 1000 type: CCpp package: gdb-headless-13.1-1.fc38 runlevel: N 5 journald_cursor: s=9b3e7e5162454feabff781758b4468ec;i=145278;b=e412b57d60c04409aa77889def5cbba0;m=10d0ba2b;t=5f759075f99e8;x=1ff2c68e782715bb comment: GDB crashes while trying to generate a stack trace for a problem report for xdg-desktop-portal-gnome backtrace_rating: 4 crash_function: quit_force executable: /usr/libexec/gdb kernel: 6.2.7-300.fc38.x86_64 Truncated backtrace: Thread no. 1 (4 frames) #40 quit_force at ../../gdb/top.c:1894 #41 captured_main_1 at ../../gdb/main.c:1311 #42 captured_main at ../../gdb/main.c:1320 #43 gdb_main at ../../gdb/main.c:1345
Created attachment 1952139 [details] File: core_backtrace
Created attachment 1952140 [details] File: cgroup
Created attachment 1952141 [details] File: open_fds
Created attachment 1952142 [details] File: backtrace
Created attachment 1952143 [details] File: dso_list
Created attachment 1952144 [details] File: maps
Created attachment 1952145 [details] File: environ
Created attachment 1952146 [details] File: cpuinfo
Created attachment 1952147 [details] File: os_info
Created attachment 1952148 [details] File: proc_pid_status
Created attachment 1952149 [details] File: limits
Created attachment 1952150 [details] File: mountinfo
Any chance of getting the core file for the xdg-desktop-portal-gnome crash?
It looks like the problem reporter deleted the core file a second after gdb crashed... So helpful. This is what I see in the systemd log: Mar 20 11:23:51 dima-dell systemd-coredump[10049]: [🡕] Process 10033 (gdb) of user 1000 dumped core. ... Mar 20 11:23:52 dima-dell abrtd[1369]: Size of '/var/spool/abrt' >= 5000 MB (MaxCrashReportsSize), deleting old directory 'ccpp-2023-03-20-10:52:34.505094-155525' Mar 20 11:23:53 dima-dell gnome-abrt[10013]: '/var/spool/abrt/ccpp-2023-03-20-10:52:34.505094-155525' does not exist Mar 20 11:23:55 dima-dell gnome-abrt[10013]: '/var/spool/abrt/ccpp-2023-03-20-10:52:34.505094-155525' does not exist Mar 20 11:23:56 dima-dell abrt-notification[10127]: [🡕] Process 10033 (gdb) crashed in ??()
Unfortunately, I don't think we'll be able to fix this without a way to reproduce it.
This does happen all the time when opening the bug report after gnome-shell crashed to send it. Shortly after this gdb crash happens to me. I sent my report, but somehow it doesn't show here?!?
The problem happen when create a report for gnome-shell reporter: libreport-2.17.11 package: gdb-headless-13.2-2.fc38 executable: /usr/libexec/gdb crash_function: quit_force kernel: 6.3.12-200.fc38.x86_64 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.freedesktop.GnomeAbrt-91795.scope type: CCpp cmdline: /usr/libexec/gdb -batch -ex $'set debuginfod enabled on' "" -ex $'file /usr/bin/gnome-shell' -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 reason: gdb killed by SIGSEGV uid: 1000 comment: The problem happen when create a report for gnome-shell journald_cursor: s=aa1aeb162c5a4917a27ad2358b45360a;i=e482f;b=d5c8adcc626342ea9974aa4bb85f1447;m=58abd811d;t=601681428fb80;x=d4de6f17854c87e1 backtrace_rating: 4 rootdir: / runlevel: N 5