Bug 92776

Summary: crash when trying to save a mail to disk
Product: [Unmaintained] kmail Reporter: Jens <jens-bugs.kde.org>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: giaracca
Priority: NOR    
Version: 1.7.1   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: mail.gz

Description Jens 2004-11-06 01:02:18 UTC
Version:           1.7.1 (using KDE 3.3.0, SuSE)
Compiler:          gcc version 3.3.4 (pre 3.3.5 20040809)
OS:                Linux (i686) release 2.6.8-24.3-default

Hello,

I am using KMail with an IMAP account and have on demand loading of attachments turned OFF (so the whole mail is loaded before it is displayed) because the demand loading is buggy. (see Bug #92745).

Just now, I looked at a mail. This mail had an attachment, which was another mail, which had a document (MS Word) attached. (actually the one that is attached at #92745..)
I tried saving the mail to disk, and KMail crashed:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1110873344 (LWP 9639)]
[KCrash handler]
#7  0x40224969 in KMFolder::getMsg () from /opt/kde3/lib/libkmailprivate.so.0
#8  0x403538f6 in KMSaveMsgCommand::slotSaveDataReq ()
   from /opt/kde3/lib/libkmailprivate.so.0
#9  0x4035d160 in KMSaveMsgCommand::qt_invoke ()
   from /opt/kde3/lib/libkmailprivate.so.0
#10 0x41a790ee in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x40fe8285 in KIO::TransferJob::dataReq () from /opt/kde3/lib/libkio.so.4
#12 0x40ff7a8b in KIO::TransferJob::slotDataReq ()
   from /opt/kde3/lib/libkio.so.4
#13 0x4101828d in KIO::TransferJob::qt_invoke () from /opt/kde3/lib/libkio.so.4
#14 0x41a790ee in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x41a79896 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x40fcdf1a in KIO::SlaveInterface::dataReq ()
   from /opt/kde3/lib/libkio.so.4
#17 0x40fff7f2 in KIO::SlaveInterface::dispatch ()
   from /opt/kde3/lib/libkio.so.4
#18 0x40fecb53 in KIO::SlaveInterface::dispatch ()
   from /opt/kde3/lib/libkio.so.4
#19 0x40fdb6eb in KIO::Slave::gotInput () from /opt/kde3/lib/libkio.so.4
#20 0x41002b9a in KIO::Slave::qt_invoke () from /opt/kde3/lib/libkio.so.4
#21 0x41a790ee in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x41a7971d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x41dc9fe0 in QSocketNotifier::activated ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x41a98d40 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x41a1685f in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x41a18423 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x416a8a91 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#28 0x41a0a9d6 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x419c3f12 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x41a2e7b1 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0x41a2e5f6 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0x41a182ef in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0x0804a9b6 in main ()


Please investigate.
If you need more information, please tell me.


Thanks a lot!
Comment 1 Till Adam 2004-11-06 22:27:17 UTC
Can you please attach the message which you tried to save to this bug report 
in zipped format. I can't get it to crash here with a self constructed 
example. Thanks

Comment 2 Jens 2004-11-08 10:00:31 UTC
Am Samstag, 6. November 2004 22:27 schrieb Till Adam:

> Can you please attach the message which you tried to save to this bug
> report in zipped format. I can't get it to crash here with a self
> constructed example. Thanks

Here you are.



Created an attachment (id=8216)
mail.gz
Comment 3 Carsten Burghardt 2004-11-13 15:36:45 UTC
I just saved this mail successfully from a courier and a cyrus imap server.
It also works with load-on-demand. Is this crash reproducable? Can you try to 
get a better backtrace with valgrind?

Comment 4 Jens 2004-11-15 11:17:40 UTC
Hi,

Sure! I haven't worked with valgrind before, though.
What parameters should I use for it to be useful for you?

Jens
Comment 5 Carsten Burghardt 2004-11-15 21:55:38 UTC
> What parameters should I use for it to be useful for you?

Just make sure you have --num-callers=50 or something to get enough 
information, the rest should be ok.

Comment 6 Jens 2004-11-16 10:25:18 UTC
Hi,

Cannot reproduce with using valgrind.
I'll reopen if I can reproduce it again. Sorry =;)

Jens
Comment 7 Till Adam 2005-01-25 21:47:00 UTC
*** Bug 97862 has been marked as a duplicate of this bug. ***