Version: 3.5.5 (using KDE KDE 3.5.5) Installed from: Gentoo Packages Compiler: gcc (GCC) 3.4.6 (Gentoo 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.10 OS: Linux I was holding the Ctrl key (while thinking), and Quanta abruptly crashed. Was editing a small files ~100 lines using PHP/HTML highlighting. I haven't been able to reproduce this at will, but it happens occasionally, and I'm always holding Ctrl when it does. Crash trace: (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1240992080 (LWP 25302)] 0xffffe410 in __kernel_vsyscall () #0 0xffffe410 in __kernel_vsyscall () #1 0xb610ce36 in nanosleep () from /lib/libc.so.6 #2 0xb610cc46 in sleep () from /lib/libc.so.6 #3 0xb6f700ba in KCrash::startDrKonqi () from /usr/kde/3.5/lib/libkdecore.so.4 #4 0x00000004 in ?? () #5 0x089865e8 in ?? () #6 0xbfc93e90 in ?? () #7 0x0840adf0 in ?? () #8 0x0854c200 in ?? () #9 0xbfc93e90 in ?? () #10 0x00000008 in ?? () #11 0xbfc93ec0 in ?? () #12 0xbfc95ed0 in ?? () #13 0xbfc93ec0 in ?? () #14 0x0854c200 in ?? () #15 0x00000011 in ?? () #16 0xbfc90020 in ?? () #17 0x0000002c in ?? () #18 0xbfc93ea8 in ?? () #19 0xb6c05d26 in QLatin1Codec::toUnicode () from /usr/qt/3/lib/libqt-mt.so.3 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Please read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports in order to improve this backtrace. This doesn't help us unfortunately.
Not enough info. Please reopen if you have followed the steps in the article.