https://bugs.kde.org/show_bug.cgi?id=503593
--- Comment #7 from Nate Graham <n...@kde.org> ---
Can confirm, and here's my more useful-looking backtrace:
#0 __pthread_kill_implementation
(threadid=<optimized out>, signo=signo@entry=11, no_tid=no_tid@entry=0) at
pthread_kill.c:44
#1 0x00007f818ac811e3 in __pthread_kill_internal (threadid=<optimized out>,
signo=11)
at pthread_kill.c:89
#2 0x00007f818ac27afe in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#3 0x00007f818e07e88a in KCrash::defaultCrashHandler (sig=11)
at /home/nate/kde/src/kcrash/src/kcrash.cpp:605
#4 0x00007f818ac27c30 in <signal handler called> () at /lib64/libc.so.6
#5 0x00007f818b08b5b9 in queue_event (display=0x18e18fe0, len=32) at
../src/wayland-client.c:1586
#6 read_events (display=0x18e18fe0) at ../src/wayland-client.c:1713
#7 wl_display_read_events (display=0x18e18fe0) at ../src/wayland-client.c:1796
#8 0x00007f818a2bb4ce in QtWaylandClient::EventThread::run (this=0x18e5e2c0)
at
/usr/src/debug/qt6-qtwayland-6.9.0-3.fc42.x86_64/src/client/qwaylanddisplay.cpp:195
#9 0x00007f818b4bdde4 in operator() (__closure=<optimized out>)
at
/usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/corelib/thread/qthread_unix.cpp:433
#10 (anonymous
namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> >
(t=<optimized out>)
at
/usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/corelib/thread/qthread_unix.cpp:365
#11 QThreadPrivate::start (arg=0x18e5e2c0)
at
/usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/corelib/thread/qthread_unix.cpp:393
#12 0x00007f818ac7f1d4 in start_thread (arg=<optimized out>) at
pthread_create.c:448
#13 0x00007f818ad01cec in __GI___clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Still not very useful though since there's no KDE code involved except for the
crash handler.
--
You are receiving this mail because:
You are watching all bug changes.
