Application: kontact (4.7.3) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-15-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: I was waiting till Kontact will become responsive after starting the program. First it checked the mail accounts, then started filtering messages in the inbox (clamscan processing among others), and when the counter of the filtered messages showed the work is almost done - CRASH. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted [Current thread is 1 (Thread 0xb77be730 (LWP 5794))] Thread 3 (Thread 0xb685ab70 (LWP 5795)): #0 0x00e9b416 in __kernel_vsyscall () #1 0x01f21a5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x00363cfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0x03779883 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0x0377999f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0x01f1dd31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0x003560ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 2 (Thread 0xb5f31b70 (LWP 5796)): #0 0x07442d10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x00c6e7d5 in do_gettime (frac=0xb5f31050, sec=0xb5f31048) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x00d414b6 in QTimerInfoList::updateCurrentTime (this=0xb560117c) at kernel/qeventdispatcher_unix.cpp:339 #4 0x00d4180a in QTimerInfoList::timerWait (this=0xb560117c, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0x00d40053 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb5f3113c) at kernel/qeventdispatcher_glib.cpp:136 #6 0x04b2888c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x04b29637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x04b29c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x00d40b37 in QEventDispatcherGlib::processEvents (this=0x892c5b8, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #10 0x00d111dd in QEventLoop::processEvents (this=0xb5f312c0, flags=...) at kernel/qeventloop.cpp:149 #11 0x00d11421 in QEventLoop::exec (this=0xb5f312c0, flags=...) at kernel/qeventloop.cpp:201 #12 0x00c1490b in QThread::exec (this=0x892b880) at thread/qthread.cpp:498 #13 0x00c149fb in QThread::run (this=0x892b880) at thread/qthread.cpp:565 #14 0x00c177b3 in QThreadPrivate::start (arg=0x892b880) at thread/qthread_unix.cpp:331 #15 0x01f1dd31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #16 0x003560ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 1 (Thread 0xb77be730 (LWP 5794)): [KCrash Handler] #7 0x00e9b416 in __kernel_vsyscall () #8 0x002b1c8f in raise () from /lib/i386-linux-gnu/libc.so.6 #9 0x002b52b5 in abort () from /lib/i386-linux-gnu/libc.so.6 #10 0x001c14ed in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #11 0x001bf283 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #12 0x001bf2bf in std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #13 0x001bf464 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #14 0x00d11569 in QEventLoop::exec (this=0xbfd8b504, flags=...) at kernel/qeventloop.cpp:214 #15 0x00d1619d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #16 0x0113d924 in QApplication::exec () at kernel/qapplication.cpp:3760 #17 0x0804ac91 in main (argc=) at ../../../kontact/src/main.cpp:218 Possible duplicates by query: bug 292160, bug 292151, bug 292113, bug 292087, bug 292078. Reported using DrKonqi
(In reply to comment #0) > The crash can be reproduced every time. > Please try the following steps to get a backtrace of the real issue: 1/ R gdb --args kontact --nofork &> ~/bug292168.txt 2/ When the gdb prompt "(gdb)" appears, enter: - "set logging file ~/bug292168.txt" - "set logging on" - "start" and wait for the prompt to reappear, then enter "break __cxa_rethrow" and finally "cont" to let the window appear. 3/ Reproduce the crash. If kontact crashes, the window will appear frozen. That's normal. 4/ in the konsole window, run "thread apply all bt" if you're prompted to continue, press enter 5/ and finally, when the "(gdb)" prompt reappears, enter "kill" then "quit" You will then find a bug292168.txt file in your home directory. Please attach it to this report.
I added a new section to summarize what to do: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash
changing status
Closing due to lack of feedback