Description of problem: I tried to debug a (firefox) problem according to [1], but after some time the backtrace process gets killed automatically, although there is enough RAM and disk space left. (gdb) thread apply all bt full [...] gdb terminated by signal ABRT. [1] https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Using_coredumpctl_to_get_backtrace Version-Release number of selected component: gdb-headless-10.1-4.fc33 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-e7978daf-55ab-4646-afd1-e889ab001a0a.scope cmdline: gdb /usr/lib64/firefox/firefox -c /var/tmp/coredump-xu18SQ crash_function: dump_core executable: /usr/libexec/gdb journald_cursor: s=e56e6cb8cfe84d05855b5ab14135c66b;i=4c9c4;b=43d2252de9b24218ba0afdcda5dec074;m=c5a309a5;t=5bec79fb3d0fc;x=7b562d4c3a4d4428 kernel: 5.11.10-200.fc33.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1474578
Created attachment 1767854 [details] File: backtrace
Created attachment 1767855 [details] File: core_backtrace
Created attachment 1767856 [details] File: cpuinfo
Created attachment 1767857 [details] File: dso_list
Created attachment 1767858 [details] File: environ
Created attachment 1767859 [details] File: limits
Created attachment 1767860 [details] File: maps
Created attachment 1767861 [details] File: mountinfo
Created attachment 1767862 [details] File: open_fds
Created attachment 1767863 [details] File: proc_pid_status
If I use gdb directly (not via coredumpcontrol/abrt) to do the backtrace of the firefox coredump file, it gives a segmentation fault. I tried to narrow the problem down and now it crashes already when I do (gdb) info threads Id Target Id Frame * 1 Thread 0x7f30975be780 (LWP 2174) 0x00007f308f7668b0 in sys_tgkill (s=11, t=2174, p=2174) at /usr/src/debug/firefox-87.0-2.fc33.x86_64/toolkit/crashreporter/google-breakpad/src/third_party/lss/linux_syscall_support.h:3555 2 Thread 0x7f306b8c1640 (LWP 2287) futex_lock_pi (private=0, abstime=0x0, futex_word=0x7f30603c2670) at ../sysdeps/nptl/futex-internal.h:412 3 Thread 0x7f3076754640 (LWP 2227) futex_wait_cancelable (private=0, expected=0, futex_word=0x7f307dd6c218) at ../sysdeps/nptl/futex-internal.h:183 4 Thread 0x7f306b04b640 (LWP 2245) futex_wait_cancelable (private=0, expected=0, futex_word=0x7f306ad0ddc8) at ../sysdeps/nptl/futex-internal.h:183 5 Thread 0x7f307f769640 (LWP 2286) syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6 Thread 0x7f306a869640 (LWP 2256) futex_wait_cancelable ( private=<error reading variable: Dwarf Error: Cannot find DIE at 0x4bdd84d2 referenced from DIE at 0x4bddbe80 [in module /usr/lib/debug/usr/lib64/firefox/libxul.so-87.0-2.fc33.x86_64.debug]>, ../../gdb/inline-frame.c:173: internal-error: void inline_frame_this_id(frame_info*, void**, frame_id*): Assertion `frame_id_p (*this_id)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) n This is a bug, please report it. For instructions, see: <https://www.gnu.org/software/gdb/bugs/>. ../../gdb/inline-frame.c:173: internal-error: void inline_frame_this_id(frame_info*, void**, frame_id*): Assertion `frame_id_p (*this_id)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) n Command aborted. (gdb) Does this really look like a problem inside gdb or is it possible that there is a problem within the firefox package, the debuginfo package or the coredump?
*** Bug 1948665 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.