Advertising
Paste Description for Lure
Another kmail crash on delete e-mail, slightly different stack trace
- Lure
- Wednesday, November 28th, 2007 at 11:35:48am MST
- Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
- [Thread debugging using libthread_db enabled]
- [New Thread -1258944832 (LWP 11390)]
- [KCrash handler]
- #6 0xb2e32849 in KMFolder::getMsgBase (this=0x0, idx=2)
- at /home/kde/src/4/KDE/kdepim/kmail/kmfolder.cpp:373
- #7 0xb2e0ae0f in KMail::HeaderItem::irefresh (this=0x92072a0)
- at /home/kde/src/4/KDE/kdepim/kmail/headeritem.cpp:104
- #8 0xb2dfc05a in KMHeaders::msgHeaderChanged (this=0x86c2850, msgId=57)
- at /home/kde/src/4/KDE/kdepim/kmail/kmheaders.cpp:1192
- #9 0xb2e00745 in KMHeaders::qt_metacall (this=0x86c2850,
- _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfc216f8)
- at /home/kde/build/4/KDE/kdepim/kmail/kmheaders.moc:149
- #10 0xb7f08c54 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
- #11 0xb7f09822 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
- #12 0xb2e33611 in KMFolder::msgHeaderChanged (this=0x85c3a60, _t1=0x85c3a60,
- _t2=57) at /home/kde/build/4/KDE/kdepim/kmail/kmfolder.moc:227
- #13 0xb2e33dd4 in KMFolder::qt_metacall (this=0x85c3a60,
- _c=QMetaObject::InvokeMetaMethod, _id=13, _a=0xbfc21c18)
- at /home/kde/build/4/KDE/kdepim/kmail/kmfolder.moc:118
- #14 0xb7f08c54 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
- #15 0xb7f09822 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
- #16 0xb2e500a3 in FolderStorage::msgHeaderChanged (this=0x85c3ba0,
- _t1=0x85c3a60, _t2=57)
- at /home/kde/build/4/KDE/kdepim/kmail/folderstorage.moc:254
- #17 0xb2e51d8a in FolderStorage::headerOfMsgChanged (this=0x85c3ba0,
- aMsg=0x8a862d0, idx=57)
- at /home/kde/src/4/KDE/kdepim/kmail/folderstorage.cpp:900
- #18 0xb2ea6c12 in KMMsgBase::setEncryptionState (this=0x8a862d0, idx=-1)
- at /home/kde/src/4/KDE/kdepim/kmail/kmmsgbase.cpp:205
- #19 0xb2d66402 in KMMessage::setEncryptionState (this=0x8a862d0,
- s=KMMsgNotEncrypted, idx=-1)
- at /home/kde/src/4/KDE/kdepim/kmail/kmmessage.cpp:3969
- #20 0xb2e4abac in KMReaderWin::parseMsg (this=0x86da6f8, aMsg=0x8a862d0)
- at /home/kde/src/4/KDE/kdepim/kmail/kmreaderwin.cpp:1524
- #21 0xb2e42961 in KMReaderWin::displayMessage (this=0x86da6f8)
- at /home/kde/src/4/KDE/kdepim/kmail/kmreaderwin.cpp:1446
- #22 0xb2e42aa0 in KMReaderWin::updateReaderWin (this=0x86da6f8)
- at /home/kde/src/4/KDE/kdepim/kmail/kmreaderwin.cpp:1385
- #23 0xb2e45c2e in KMReaderWin::qt_metacall (this=0x86da6f8,
- _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfc22080)
- at /home/kde/build/4/KDE/kdepim/kmail/kmreaderwin.moc:161
- #24 0xb7f08c54 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
- #25 0xb7f09822 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
- #26 0xb7f270d7 in QTimer::timeout () from /usr/lib/libQtCore.so.4
- #27 0xb7f0f7ee in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
- #28 0xb7f07814 in QObject::event () from /usr/lib/libQtCore.so.4
- #29 0xb6fa54ed in QApplicationPrivate::notify_helper ()
- from /usr/lib/libQtGui.so.4
- #30 0xb6fa8f27 in QApplication::notify () from /usr/lib/libQtGui.so.4
- #31 0xb7aae065 in KApplication::notify (this=0xbfc22ba8, receiver=0x86da748,
- event=0xbfc22948)
- at /home/kde/src/4/KDE/kdelibs/kdeui/kernel/kapplication.cpp:319
- #32 0xb7ef5c4b in QCoreApplication::notifyInternal ()
- from /usr/lib/libQtCore.so.4
- #33 0xb7f1cde9 in ?? () from /usr/lib/libQtCore.so.4
- #34 0xbfc22ba8 in ?? ()
- #35 0x086da748 in ?? ()
- #36 0xbfc22948 in ?? ()
- #37 0xb7ef771d in QCoreApplication::sendPostedEvents ()
- from /usr/lib/libQtCore.so.4
- #38 0xb7f19900 in ?? () from /usr/lib/libQtCore.so.4
- #39 0x08068674 in ?? ()
- #40 0xb593121c in ?? () from /usr/lib/libglib-2.0.so.0
- #41 0xbfc229d8 in ?? ()
- #42 0xb58a2366 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
- Backtrace stopped: frame did not save the PC
- #0 0xffffe410 in __kernel_vsyscall ()
advertising
Update the Post
Either update this post and resubmit it with changes, or make a new post.
You may also comment on this post.
Please note that information posted here will expire by default in one month. If you do not want it to expire, please set the expiry time above. If it is set to expire, web search engines will not be allowed to index it prior to it expiring. Items that are not marked to expire will be indexable by search engines. Be careful with your passwords. All illegal activities will be reported and any information will be handed over to the authorities, so be good.