Hello, since I upgraded from kmail 3.5.0 to 3.5.2 I've had this problem where kmail will crash if you try to view the source of a message without opening the message first. If you select a message in the Inbox or another folder, then either go to View-View Source or just use the 'v' shortcut key, kmail will crash. If you use the kmail component in kontact, this will crash kontact as well. It doesn't matter whether the message is in a folder on my imap acct. or in a local folder, it will crash either way. I've upgraded to kmail 3.5.2-r1 and this problem remains. I am using amd64. Here is a backtrace generated after I try to view a message source: [code]Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 27084)] [New Thread 32769 (LWP 27085)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 27084)] [New Thread 32769 (LWP 27085)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 27084)] [New Thread 32769 (LWP 27085)] [New Thread 16386 (LWP 27086)] [New Thread 32771 (LWP 27087)] [New Thread 49156 (LWP 27088)] [New Thread 65541 (LWP 27089)] 0x00002aaab0461a05 in nanosleep () from /lib/libc.so.6 #0 0x00002aaab0461a05 in nanosleep () from /lib/libc.so.6 #1 0x00002aaab04618a2 in sleep () from /lib/libc.so.6 #2 0x00002aaaad7787ea in KCrash::startDrKonqi(char const**, int) () from /usr/kde/3.5/lib64/libkdecore.so.4 #3 0x00002aaaad778b1e in KCrash::defaultCrashHandler(int) () from /usr/kde/3.5/lib64/libkdecore.so.4 #4 0x00002aaaafdcc107 in __pthread_sighandler () from /lib/libpthread.so.0 #5 0x00002aaab0405810 in killpg () from /lib/libc.so.6[/code]
Still an issue, assured that you use the latest kde-base/* ebuild revisions? If so, pleas provide a usable backtrace http://www.gentoo.org/proj/en/qa/backtraces.xml
I have upgraded to kmail-3.5.2-r2 and kdelibs-3.5.2-r4 and the problem persists. The backgrace displayed by Dr.Konqi is different now, but evidently it is not useful? ############# This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912614467808 (LWP 11757)] [New Thread 1107310944 (LWP 11761)] [Thread debugging using libthread_db enabled] [New Thread 46912614467808 (LWP 11757)] [New Thread 1107310944 (LWP 11761)] [Thread debugging using libthread_db enabled] [New Thread 46912614467808 (LWP 11757)] [New Thread 1107310944 (LWP 11761)] [New Thread 1098918240 (LWP 11760)] [New Thread 1090525536 (LWP 11759)] [New Thread 1082132832 (LWP 11758)] 0x00002aaab19e6c65 in nanosleep () from /lib/tls/libc.so.6 #0 0x00002aaab19e6c65 in nanosleep () from /lib/tls/libc.so.6 #1 0x00002aaab19e6ad0 in sleep () from /lib/tls/libc.so.6 #2 0x00002aaaaeb8123c in KCrash::startDrKonqi(char const**, int) ( argv=0x7fffffd2f1b0, argc=17) at kcrash.cpp:311 #3 0x00002aaaaeb81548 in KCrash::defaultCrashHandler(int) (sig=-2947536) at kcrash.cpp:228 #4 0x00002aaab19877f0 in killpg () from /lib/tls/libc.so.6 ####################### I emerged kmail and kdelibs with the +debug flag set, and I had the following set in make.conf per the instruction: CFLAGS="-march=athlon64 -pipe -O2 -ggdb" FEATURES="nostrip" Yet I still get the warning about the backtrace being unuseful. Is this normal?
It looks like you did everything okay. I'm not sure why it's not giving more useful results. Can you try emerging "gdb" and running kmail in gdb. Something like: emerge gdb gdb kmail run (cause it to crash) bt That will display the backtrace outside of the dr. konqi stuff.
I had to use "run --nofork --nocrashhandler" in gdb, but I got the backtrace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 46912614467808 (LWP 31782)] KMReaderWin::setUpdateAttachment(bool) (this=0x0) at kmreaderwin.h:250 250 kmreaderwin.h: No such file or directory. in kmreaderwin.h (gdb) bt #0 KMReaderWin::setUpdateAttachment(bool) (this=0x0) at kmreaderwin.h:250 #1 0x00002aaaab057d99 in KMMainWidget::slotShowMsgSrc() (this=0xb70ae0) at kmmainwidget.cpp:2866 #2 0x00002aaaab063359 in KMMainWidget::qt_invoke(int, QUObject*) (this=0xb70ae0, _id=124, _o=0x7fffffb8a160) at kmmainwidget.moc:547 #3 0x00002aaaaf7fc238 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/qt/3/lib64/libqt-mt.so.3 #4 0x00002aaaaf7fc9a2 in QObject::activate_signal(int) () from /usr/qt/3/lib64/libqt-mt.so.3 #5 0x00002aaaae4a9a9f in KAction::qt_invoke(int, QUObject*) (this=0xc18020, _id=15, _o=0x7fffffb8a220) at kaction.moc:218 #6 0x00002aaaaf7fc238 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/qt/3/lib64/libqt-mt.so.3 #7 0x00002aaaaf7fc9a2 in QObject::activate_signal(int) () from /usr/qt/3/lib64/libqt-mt.so.3 #8 0x00002aaaaeb76e20 in KAccelPrivate::emitActivatedSignal(KAccelAction*) (this=0xc22750, pAction=0xcd00e0) at kaccel.cpp:400 #9 0x00002aaaaeb77c93 in KAccelPrivate::eventFilter(QObject*, QEvent*) (this=0xc22750, pEvent=0x7fffffb8a770) at kaccel.cpp:370 #10 0x00002aaaaf7f9927 in QObject::activate_filters(QEvent*) () from /usr/qt/3/lib64/libqt-mt.so.3 #11 0x00002aaaaf7f9a0e in QObject::event(QEvent*) () from /usr/qt/3/lib64/libqt-mt.so.3 #12 0x00002aaaaf82de83 in QWidget::event(QEvent*) () from /usr/qt/3/lib64/libqt-mt.so.3 #13 0x00002aaaaf8d85f5 in QMainWindow::event(QEvent*) () from /usr/qt/3/lib64/libqt-mt.so.3 #14 0x00002aaaaf7a36ad in QApplication::internalNotify(QObject*, QEvent*) () from /usr/qt/3/lib64/libqt-mt.so.3 #15 0x00002aaaaf7a3cc1 in QApplication::notify(QObject*, QEvent*) () from /usr/qt/3/lib64/libqt-mt.so.3 #16 0x00002aaaaeb0ce8c in KApplication::notify(QObject*, QEvent*) (this=0x7fffffb8ae20, receiver=0xbae380, event=0x7fffffb8a770) at kapplication.cpp:550 ---Type <return> to continue, or q <return> to quit--- #17 0x00002aaaab5e0e85 in QApplication::sendEvent(QObject*, QEvent*) (receiver=0x2aaaafde42e0, event=0x0) at qapplication.h:491 #18 0x00002aaaaeb757b6 in KAccelEventHandler::x11Event(_XEvent*) (this=0x0, pEvent=0x2aaaaedb0358) at kaccel.cpp:144 #19 0x00002aaaaeb1643d in KAppX11HackWidget::publicx11Event(_XEvent*) (this=0x0, e=0x0) at kapplication.cpp:1651 #20 0x00002aaaaeb0ea67 in KApplication::x11EventFilter(_XEvent*) (this=0x7fffffb8ae20, _event=0x7fffffb8ab40) at kapplication.cpp:1721 #21 0x00002aaaaf73b1b1 in qt_set_x11_event_filter(int (*)(_XEvent*)) () from /usr/qt/3/lib64/libqt-mt.so.3 #22 0x00002aaaaf747528 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/qt/3/lib64/libqt-mt.so.3 #23 0x00002aaaaf75927b in QEventLoop::processEvents(unsigned) () from /usr/qt/3/lib64/libqt-mt.so.3 #24 0x00002aaaaf7b7825 in QEventLoop::enterLoop() () from /usr/qt/3/lib64/libqt-mt.so.3 #25 0x00002aaaaf7b7782 in QEventLoop::exec() () from /usr/qt/3/lib64/libqt-mt.so.3 #26 0x0000000000403440 in main (argc=-4674432, argv=0x7fffffb8b138) at main.cpp:110 (gdb)
I have just upgraded to kde-base/kmail-3.5.2-r3 and this problem persists.
I've installed kmail-3.5.3 and I'm happy to report this problem is gone.
