Application that crashed: kontact
Version of the application: 4.3.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.1
Operating System: Linux 2.6.29-gentoo-r5 x86_64

What I was doing when the application crashed:
Kontact crashed with a segfault when I tried to open a message in a DIMAP folder via mouse click...

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 0 (LWP 26524)]

Thread 2 (Thread 0x7fe1a9b6d950 (LWP 26153)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:217
#1  0x00007fe1c060a617 in QWaitCondition::wait (this=0x1f0eef8, mutex=0x1f0eef0, time=30000) at thread/qwaitcondition_unix.cpp:85
#2  0x00007fe1c06017f9 in QThreadPoolThread::run (this=0x1f0e130) at concurrent/qthreadpool.cpp:140
#3  0x00007fe1c06098b9 in QThreadPrivate::start (arg=0x1f0e130) at thread/qthread_unix.cpp:189
#4  0x00007fe1c0398ff7 in start_thread (arg=<value optimized out>) at pthread_create.c:297
#5  0x00007fe1bf96748d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fe1c65bd750 (LWP 26524)):
[KCrash Handler]
#5  0x00007fe1af475c4e in KMReaderWin::parseMsg (this=0x16fdef0, aMsg=0x42823b0) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/kmreaderwin.cpp:1667
#6  0x00007fe1af4626fa in KMReaderWin::displayMessage (this=0x16fdef0) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/kmreaderwin.cpp:1589
#7  0x00007fe1af4628e5 in KMReaderWin::updateReaderWin (this=0x16fdef0) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/kmreaderwin.cpp:1529
#8  0x00007fe1af471135 in KMReaderWin::qt_metacall (this=0x16fdef0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffce60bd70)
    at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0_build/kmail/kmreaderwin.moc:165
#9  0x00007fe1c06efe4d in QMetaObject::activate (sender=0x16fdf88, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x1) at kernel/qobject.cpp:3108
#10 0x00007fe1c06ec4e3 in QObject::event (this=0x16fdf88, e=0x46) at kernel/qobject.cpp:1073
#11 0x00007fe1c122e65d in QApplicationPrivate::notify_helper (this=0x1116850, receiver=0x16fdf88, e=0x7fffce60c410) at kernel/qapplication.cpp:4057
#12 0x00007fe1c123704a in QApplication::notify (this=0x7fffce60c860, receiver=0x16fdf88, e=0x7fffce60c410) at kernel/qapplication.cpp:4022
#13 0x00007fe1c1ff8fab in KApplication::notify (this=0x7fffce60c860, receiver=0x16fdf88, event=0x7fffce60c410)
    at /var/tmp/portage/kde-base/kdelibs-4.3.0-r1/work/kdelibs-4.3.0/kdeui/kernel/kapplication.cpp:302
#14 0x00007fe1c06dda1b in QCoreApplication::notifyInternal (this=0x7fffce60c860, receiver=0x16fdf88, event=0x7fffce60c410) at kernel/qcoreapplication.cpp:606
#15 0x00007fe1c070612e in QTimerInfoList::activateTimers (this=0x110d290) at kernel/qcoreapplication.h:213
#16 0x00007fe1c0702f2d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#17 0x00007fe1bbb07bf6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#18 0x00007fe1bbb0ade5 in ?? () from /usr/lib/libglib-2.0.so.0
#19 0x00007fe1bbb0aff7 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#20 0x00007fe1c0702e8f in QEventDispatcherGlib::processEvents (this=0x11163c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#21 0x00007fe1c12b481f in QGuiEventDispatcherGlib::processEvents (this=0x42823b0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#22 0x00007fe1c06dc3d2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -832518528}) at kernel/qeventloop.cpp:149
#23 0x00007fe1c06dc565 in QEventLoop::exec (this=0x7fffce60c6c0, flags={i = -832518448}) at kernel/qeventloop.cpp:196
#24 0x00007fe1c06de5fc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#25 0x0000000000404b59 in main (argc=1, argv=0x7fffce60ce38) at /var/tmp/portage/kde-base/kontact-4.3.0/work/kontact-4.3.0/kontact/src/main.cpp:218

This bug may be a duplicate of or related to bug 201024

Reported using DrKonqi