Description of problem: Dr Konqi was trying to generate a backtrace after plasmashell crashed (plasmashell crash was likely: https://bugzilla.redhat.com/show_bug.cgi?id=2185282). Dr Konqi crashed trying to generate the backtrace. Version-Release number of selected component: gdb-headless-13.2-5.fc38 Additional info: reporter: libreport-2.17.11 type: CCpp reason: gdb killed by SIGABRT journald_cursor: s=817971a5930643a58c407d18bbf24d1d;i=8df8b;b=4ca4965308c04052af6db7a7a7cc07e8;m=a981f37e;t=60715c6085322;x=919866639df6cc06 executable: /usr/libexec/gdb cmdline: /usr/bin/gdb -nw -n -batch -x /tmp/drkonqi.qZOSHS -x /tmp/drkonqi.OakIGM -p 12990 /usr/bin/plasmashell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/plasma-plasmashell.service rootdir: / uid: 1000 kernel: 6.5.5-200.fc38.x86_64 package: gdb-headless-13.2-5.fc38 runlevel: N 5 backtrace_rating: 3 crash_function: handle_fatal_signal comment: Dr Konqi was trying to generate a backtrace after plasmashell crashed (plasmashell crash was likely: https://bugzilla.redhat.com/show_bug.cgi?id=2185282). Dr Konqi crashed trying to generate the backtrace. Truncated backtrace: Thread no. 1 (10 frames) #3 handle_fatal_signal at ../../gdb/event-top.c:985 #5 __futex_abstimed_wait_common64 at futex-internal.c:57 #6 __futex_abstimed_wait_common at futex-internal.c:87 #7 __futex_abstimed_wait_cancelable64 at futex-internal.c:139 #8 __pthread_cond_wait_common at pthread_cond_wait.c:503 #9 ___pthread_cond_wait at pthread_cond_wait.c:618 #10 std::condition_variable::wait(std::unique_lock<std::mutex>&) #11 gdb::thread_pool::thread_function at ../../gdbsupport/thread-pool.cc:235 #12 execute_native_thread_routine #14 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Created attachment 1992588 [details] File: proc_pid_status
Created attachment 1992589 [details] File: maps
Created attachment 1992590 [details] File: limits
Created attachment 1992591 [details] File: environ
Created attachment 1992592 [details] File: open_fds
Created attachment 1992593 [details] File: mountinfo
Created attachment 1992594 [details] File: os_info
Created attachment 1992595 [details] File: cpuinfo
Created attachment 1992596 [details] File: core_backtrace
Created attachment 1992597 [details] File: dso_list
Created attachment 1992598 [details] File: var_log_messages
Created attachment 1992599 [details] File: backtrace
Do you have the core file from the crashing application (plasmashell)? If so, could you upload it?
I have a coredump in the problem directory, would that be the one you need? It's > 600 MB though but I've compressed it down to ~80 MB. It's available here: https://drive.google.com/file/d/19kUoEspwZdUE3pSrjaJ-ShQs7FIi_k5G/view?usp=sharing I hope this helps, let me know if I can provide anything else.
Usually these GDB abrt bugs occur when GDB is used to obtain a backtrace from a core file created by an application. That's not the case for this bug, as GDB was used to attach to a running process. So, unfortunately, there's no way for me to reproduce this bug.