Description of problem: Crashed during error reporting. Version-Release number of selected component: gdb-headless-8.2-6.fc29 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/gdb -batch -iex add-auto-load-safe-path /var/cache/abrt-di/usr/lib/debug -iex add-auto-load-scripts-directory /var/cache/abrt-di/usr/lib/debug -ex set debug-file-directory /usr/lib/debug:/var/cache/abrt-di/usr/lib/debug -ex file /usr/bin/gnome-software -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 crash_function: dump_core executable: /usr/libexec/gdb journald_cursor: s=72bed2efddf844b4a6d63d093f3d6e56;i=1c40;b=57ee5ef2b0214c48950c436040e7a829;m=140a3ffd;t=58320d05cf762;x=8e5e61524ed55b01 kernel: 4.20.13-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1544195
Created attachment 1540148 [details] File: backtrace
Created attachment 1540149 [details] File: cgroup
Created attachment 1540150 [details] File: core_backtrace
Created attachment 1540151 [details] File: cpuinfo
Created attachment 1540152 [details] File: dso_list
Created attachment 1540153 [details] File: environ
Created attachment 1540154 [details] File: limits
Created attachment 1540155 [details] File: maps
Created attachment 1540156 [details] File: mountinfo
Created attachment 1540157 [details] File: open_fds
Created attachment 1540158 [details] File: proc_pid_status
It looks like we have an(other) assertion failure in the dwarf reader (at dwarf2read.c:5263) in dw2_find_pc_sect_compunit_symtab. Is it possible for you to share a reproducer for this?
Puh. Sorry, no. Did not happen again :-(
*** Bug 1696834 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Within a sourced Python script, running `gdb.execute('quit')` during an exit event handler causes a segfault. To reproduce, run gdb on any executable after sourcing this Python script: def on_exit(event): gdb.execute('quit') gdb.events.exited.connect(on_exit) When the inferior ends, gdb should quit, but it segfaults instead. This happens on gdb 8.2 and newer. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/gdb -nx -q -x on_exit.py -ex run simple_race crash_function: dump_core executable: /usr/libexec/gdb journald_cursor: s=c228e1adbf734ffb85d748f6f7e66196;i=cb180;b=ff62d51eb4f146d2b9d6cc9cc0f1293f;m=2edde00e02;t=5869b732947f2;x=4ffe5fc8a1bad054 kernel: 5.0.6-200.fc29.x86_64 package: gdb-headless-8.2-6.fc29 reason: gdb killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was reporting a crash of gnome-software. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/gdb -batch -iex add-auto-load-safe-path /var/cache/abrt-di/usr/lib/debug -iex add-auto-load-scripts-directory /var/cache/abrt-di/usr/lib/debug -ex set debug-file-directory /usr/lib/debug:/var/cache/abrt-di/usr/lib/debug -ex file /usr/bin/gnome-software -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 crash_function: dump_core executable: /usr/libexec/gdb journald_cursor: s=6f09346979c44dee969a84c5eb980a0f;i=184d6c;b=4bb9c7e4c5b04f1194e43d255781aba0;m=1dc76ab5;t=5873cd5d369ab;x=9bf0642131aa5496 kernel: 5.0.7-200.fc29.x86_64 package: gdb-headless-8.2-6.fc29 reason: gdb killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1689137 has been marked as a duplicate of this bug. ***
*** Bug 1758802 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.