Description of problem: I was playing fallout76 and this crashed so it got laggy Version-Release number of selected component: gdb-headless-13.1-3.fc38 Additional info: reporter: libreport-2.17.9 kernel: 6.2.9-300.fc38.x86_64 reason: gdb killed by SIGSEGV backtrace_rating: 4 journald_cursor: s=98762b426df54e25b73ad9d993d13ba6;i=9e5f9;b=cb0ee3024ba3451ba58d4611eb3db8e8;m=d6f28a7a2;t=5f8ef0ff1545e;x=aeb457c17e68e742 package: gdb-headless-13.1-3.fc38 executable: /usr/libexec/gdb cmdline: /usr/libexec/gdb -batch -ex $'set debuginfod enabled on' "" -ex $'file /usr/lib64/firefox/firefox' -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 comment: I was playing fallout76 and this crashed so it got laggy cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.freedesktop.problems.applet rootdir: / runlevel: N 5 crash_function: internal_vproblem(internal_problem *, const char *, int, const char *, typedef __va_list_tag __va_list_tag *) type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #505 internal_vproblem(internal_problem *, const char *, int, const char *, typedef __va_list_tag __va_list_tag *) at ../../gdb/utils.c:352 #506 internal_verror at ../../gdb/utils.c:476 #507 internal_error_loc at ../../gdbsupport/errors.cc:58 #508 ui_file::write_async_safe at ../../gdb/ui-file.h:70 #509 handle_fatal_signal at ../../gdb/event-top.c:957 #511 __pthread_kill_implementation at pthread_kill.c:44
Created attachment 1956514 [details] File: mountinfo
Created attachment 1956515 [details] File: dso_list
Created attachment 1956516 [details] File: cpuinfo
Created attachment 1956517 [details] File: backtrace
Created attachment 1956518 [details] File: environ
Created attachment 1956519 [details] File: exploitable
Created attachment 1956520 [details] File: open_fds
Created attachment 1956521 [details] File: proc_pid_status
Created attachment 1956522 [details] File: core_backtrace
Created attachment 1956523 [details] File: maps
Created attachment 1956524 [details] File: os_info
Created attachment 1956525 [details] File: limits
Hi Tony, are there any chances you have a coredump that makes GDB crash? I believe abrt should create core dumps if creating them is not disabled. Try looking for them at /var/spool/abrt/ccpp-_date_something/, on my machine I have ccpp-2023-05-02-14:17:58.588529-473184 for example. These directories are probably being cleaned up regulary so the coredumps you're looking for are not staying there for long. Thank you, Alexandra