Summary: | kmail shows empty folder index and crashes when clicking on a mail | ||
---|---|---|---|
Product: | [Applications] kmail | Reporter: | Jens <jens-bugs.kde.org> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 1.7.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Screenshot showing the folder index |
Description
Jens
2004-11-17 12:11:11 UTC
Created attachment 8313 [details]
Screenshot showing the folder index
Just happened again. this time, I sent an email which was saved to the same folder (IMAP), the folder view updated but all the mails vanished. Double clicking on one mail crashed KMail. Is it possible to attach valgrind to a running KMail? Because I tried valgrind and KMail gets so slow that it is not possible having it run under valgrind all the time. Here's a gdb output: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 1760)] 0x40297ff5 in KMMsgBase::transferInProgress () from /opt/kde3/lib/libkmailprivate.so.0 (gdb) bt 20 #0 0x40297ff5 in KMMsgBase::transferInProgress () from /opt/kde3/lib/libkmailprivate.so.0 #1 0x401ecc7a in KMHeaders::selectMessage () from /opt/kde3/lib/libkmailprivate.so.0 #2 0x401f6050 in KMHeaders::qt_invoke () from /opt/kde3/lib/libkmailprivate.so.0 #3 0x41a3b13e in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #4 0x41d94495 in QListView::doubleClicked () from /usr/lib/qt3/lib/libqt-mt.so.3 #5 0x414248c8 in KListView::contentsMouseDoubleClickEvent () from /opt/kde3/lib/libkdeui.so.4 #6 0x41b53a12 in QScrollView::viewportMouseDoubleClickEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #7 0x41b54eb6 in QScrollView::eventFilter () from /usr/lib/qt3/lib/libqt-mt.so.3 #8 0x41b24d88 in QListView::eventFilter () from /usr/lib/qt3/lib/libqt-mt.so.3 #9 0x401f6d70 in KMHeaders::eventFilter () from /opt/kde3/lib/libkmailprivate.so.0 #10 0x41a3b9de in QObject::activate_filters () from /usr/lib/qt3/lib/libqt-mt.so.3 #11 0x41a3bac0 in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #12 0x41a706af in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #13 0x419d940f in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #14 0x419db778 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #15 0x41673d5e in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #16 0x41977dc3 in QETWidget::translateMouseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #17 0x41976c9d in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #18 0x419875d5 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #19 0x419f1071 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 (More stack frames follow...) > Is it possible to attach valgrind to a running KMail?
No that is not possible - valgrind is a CPU emulator, it needs to run kmail from the start.
But if it happens that often, you can certainly run kmail in valgrind
valgrind --tool=memcheck --num-callers=50 kmail --nofork 2>&1 | tee log
|