Bug 97344 - Expiring certain folder causes crash
Summary: Expiring certain folder causes crash
Status: RESOLVED DUPLICATE of bug 90320
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-18 14:51 UTC by Phil Rigby
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Phil Rigby 2005-01-18 14:51:04 UTC
Version:            (using KDE KDE 3.3.91)
Installed from:    Compiled From Sources
OS:                Linux

I have a "spam" folder where all my junk goes into... I'd just started KMail (from 3.4 beta 1), right-clicked the Spam folder and expired it - KMail crashed, here's the backtrace:-

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread 1097917216 (LWP 4450)]
[KCrash handler]
#4  0x00000021 in ?? ()
#5  0x40349a23 in KMMoveCommand::execute (this=0x851b7b8)
    at kmcommands.cpp:1798
#6  0x40341d85 in KMCommand::slotPostTransfer (this=0x851b7b8, 
    result=KMCommand::OK) at kmcommands.cpp:202
#7  0x40344d94 in KMCommand::qt_invoke (this=0x851b7b8, _id=5, _o=0xbfffef10)
    at qucom_p.h:312
#8  0x40344f99 in KMMenuCommand::qt_invoke (this=0x851b7b8, _id=5, 
    _o=0xbfffef10) at kmcommands.moc:2509
#9  0x40348b7a in KMMoveCommand::qt_invoke (this=0x851b7b8, _id=5, 
    _o=0xbfffef10) at kmcommands.moc:2676
#10 0x49fd13a0 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#11 0x4033a0bc in KMCommand::messagesTransfered (this=0x851b7b8, 
    t0=KMCommand::OK) at kmcommands.moc:126
#12 0x4034082f in KMCommand::transferSelectedMsgs (this=0x851b7b8)
    at kmcommands.cpp:296
#13 0x403449fb in KMCommand::slotStart (this=0x851b7b8) at kmcommands.cpp:194
#14 0x40344d82 in KMCommand::qt_invoke (this=0x851b7b8, _id=4, _o=0xbffff180)
    at kmcommands.moc:147
#15 0x40344f99 in KMMenuCommand::qt_invoke (this=0x851b7b8, _id=4, 
    _o=0xbffff180) at kmcommands.moc:2509
#16 0x40348b7a in KMMoveCommand::qt_invoke (this=0x851b7b8, _id=4, 
    _o=0xbffff180) at kmcommands.moc:2676
#17 0x49fd13a0 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#18 0x4a30259d in QSignal::signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x49fea0dd in QSignal::activate () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x49ff119b in QSingleShotTimer::event ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#21 0x49f72849 in QApplication::internalNotify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x49f729da in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#23 0x40524df0 in KApplication::notify (this=0xbffff8e0, receiver=0x824b678, 
    event=0xbffff590) at kapplication.cpp:548
#24 0x49f66bbe in QEventLoop::activateTimers ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x49f22bde in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#26 0x49f87e75 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#27 0x49f87dce in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#28 0x49f71a4b in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#29 0x0804a3c3 in main (argc=3, argv=0xbffffaa4) at kapplication.h:218


I know bugs have been reported before like this and been resolved, just thought I'd post this because it's a newer version of KMail than those previously.

I haven't tried to reproduce the problem yet, thought I'd post first before the backtrace disappeared for some reason :-)

Phil.
Comment 1 Phil Rigby 2005-01-23 23:41:44 UTC
Have been able to reproduce this, several times.
Comment 2 David Faure 2005-01-24 00:23:35 UTC
Same backtrace as in 90320, and both are about deleting mails [although not the same way]. Till fixed this in CVS recently.

*** This bug has been marked as a duplicate of 90320 ***