https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #14 from Robin Bankhead <kde.b...@headbank.co.uk> --- (In reply to fanzhuyifan from comment #6) > When kglobalacceld uses 100% of CPU, could you attach a gdb instance to it, > press Ctrl-C, and upload the results of `thread apply all backtrace full`? > This is to see where kglobalacceld is stuck at. You would need to install > debug symbols. > > Could you reattach the logs if you add the following environment variable > before running kglobalacceld? > QT_LOGGING_RULES="kf.globalaccel.kglobalacceld.debug=true" > > Thanks! Output below: ---------------------------------- robin@lentoo ~ $ gdb -p `pidof kglobalacceld` GNU gdb (Gentoo 15.1 vanilla) 15.1 Copyright (C) 2024 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://bugs.gentoo.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". Attaching to process 3000 [New LWP 3028] [New LWP 3021] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007f9fc6668180 in ?? () from /usr/lib64/libglib-2.0.so.0 (gdb) Quit (gdb) thread apply all backtrace full Thread 3 (Thread 0x7f9fc20006c0 (LWP 3021) "QDBusConnection"): #0 0x00007f9fc6d2266f in poll () at /lib64/libc.so.6 #1 0x00007f9fc666b8d7 in ??? () at /usr/lib64/libglib-2.0.so.0 #2 0x00007f9fc666bfa0 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007f9fc72c1670 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt6Core.so.6 #4 0x00007f9fc750f2aa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt6Core.so.6 #5 0x00007f9fc744c8c0 in QThread::exec() () at /usr/lib64/libQt6Core.so.6 #6 0x00007f9fc6a65b8e in ??? () at /usr/lib64/libQt6DBus.so.6 #7 0x00007f9fc73ee76a in ??? () at /usr/lib64/libQt6Core.so.6 #8 0x00007f9fc6cc3379 in ??? () at /lib64/libc.so.6 #9 0x00007f9fc6d2f2cc in ??? () at /lib64/libc.so.6 Thread 2 (Thread 0x7f9fc16006c0 (LWP 3028) "QXcbEventQueue"): #0 0x00007f9fc6d2266f in poll () at /lib64/libc.so.6 #1 0x00007f9fc5b1c4a2 in ??? () at /usr/lib64/libxcb.so.1 #2 0x00007f9fc5b1e86a in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x00007f9fc2d7b418 in ??? () at /usr/lib64/qt6/plugins/platforms/../../../libQt6XcbQpa.so.6 #4 0x00007f9fc73ee76a in ??? () at /usr/lib64/libQt6Core.so.6 #5 0x00007f9fc6cc3379 in ??? () at /lib64/libc.so.6 #6 0x00007f9fc6d2f2cc in ??? () at /lib64/libc.so.6 Thread 1 (Thread 0x7f9fc2ddce40 (LWP 3000) "kglobalacceld"): #0 0x00007f9fc6668180 in ??? () at /usr/lib64/libglib-2.0.so.0 #1 0x00007f9fc6669fed in ??? () at /usr/lib64/libglib-2.0.so.0 #2 0x00007f9fc666b4dc in ??? () at /usr/lib64/libglib-2.0.so.0 #3 0x00007f9fc666b816 in ??? () at /usr/lib64/libglib-2.0.so.0 #4 0x00007f9fc666bfa0 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x00007f9fc72c1670 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt6Core.so.6 #6 0x00007f9fc750f2aa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt6Core.so.6 #7 0x00007f9fc750f45a in QCoreApplication::exec() () at /usr/lib64/libQt6Core.so.6 #8 0x0000558d983bfa9c in main () ----------------------------- Guessing you will need me to obtain symbols for other libs shown above? (As mentioned I need to recompile packages to get them, yay Gentoo). -- You are receiving this mail because: You are watching all bug changes.
