Bug 168911

Summary:	Kmail chrashes when trying to forward a message
Product:	[Applications] kmail	Reporter:	Alexander Viehl <viehl>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED LATER
Severity:	crash	CC:	christophe, Regnaron
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description Alexander Viehl 2008-08-11 15:10:07 UTC

Version:            (using KDE 4.1.0)
Installed from:    SuSE RPMs
OS:                Linux

I am using Kmail 4.1.0 on openSuse 11.0 (x86_64)
The emails are located at an exchange server, the connection type is IMAP.

After clicking on the "forward message" button (a "normal" message with 4 attachments of less than 1MB, Kmail suddenly crashes with the attached error message output.


Application: KMail (kmail), signal SIGSEGV
 [?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f0c7921f700 (LWP 23801)]
[New Thread 0x41adc950 (LWP 23916)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00007f0c6ce3afe7 in memcpy () from /lib64/libc.so.6
#6  0x00007f0c725d1c3c in QListData::detach2 () from /usr/lib64/libQtCore.so.4
#7  0x00007f0c788e0479 in ?? () from /usr/lib64/libkmailprivate.so.4
#8  0x0000000000000000 in ?? ()
#0  0x00007f0c6ce5c261 in nanosleep () from /lib64/libc.so.6

Comment 1 Oliver Putz 2008-08-11 15:58:57 UTC

Hello,

Thanks for your report. Unfortunately your backtrace is not really usable as is. Can you have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and try to install the debugging packages for your distribution? Can you reproduce the crash? If so, how exactly (forwarding works for me here)?

Comment 2 Alexander Viehl 2008-08-11 16:04:24 UTC

I will install the debugging packages.
I can not reproduce this bug, but I will try to report all bugs and crashes. (I use Kmail 4.1 as my default mail tool and I use it intensively)
It seems, Kmail often crashes when the system has high load or when more than one action is running in parallel (e.g. fetching folder contents and forwarding mails)
I will try to reproduce the bug with the debuggin packages.

Comment 3 Christophe Marin 2008-11-19 14:38:10 UTC

> I will try to reproduce the bug with the debuggin packages. 

Thank you. Feel free to reopen this bug when you experience this bug again.