Bug 109410 - IMAP kioslave crashes when trying to download a message
Summary: IMAP kioslave crashes when trying to download a message
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-21 12:16 UTC by Arne Schmitz
Modified: 2012-08-19 12:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arne Schmitz 2005-07-21 12:16:17 UTC
Version:           Unbekannt (using KDE 3.4.1 Level "a" , SUSE 9.3 UNSUPPORTED)
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
OS:                Linux (i686) release 2.6.11.4-21.7-default

I am using the GMX IMAP service. Whenever I upload a message via KMail or move a message (e.g. deleting it), the IMAP kioslave crashes with the message:

QGArray::at: Absolute index 0 out of range
kioslave: ####### CRASH ###### protocol = imaps pid = 9177 signal = 11
Comment 1 Arne Schmitz 2005-07-21 12:17:14 UTC
Oh, btw: if the folder contains only received (not uploaded) messages, everything works fine.
Comment 2 Carsten Burghardt 2005-07-21 15:08:54 UTC
It would be great if could get a backtrace from the kioslave to see what's
going wrong:
http://websvn.kde.org/trunk/KDE/kdebase/kioslave/DEBUG.howto?rev=409203&view=markup
Comment 3 Ted Lemon 2005-10-07 09:03:08 UTC
A couple of comments on this.   First, the debugging HOWTO doesn't quite work - if you follow the directions there, the kioslave process just dies.   What I was able to do, since the IMAP slave runs for quite a while before it hits a problem, was to continue it and *then* attach GDB to it, using the process ID that kdeinit prints.   I don't know why this isn't working - possibly a difference in behavior between Linux kernels?

Here's the stack trace that I get.   There's a bunch of crap above the kdemain(), but that looks like it's just garbage.

#0  0xb763f529 in QBuffer::writeBlock () from /usr/lib/libqt-mt.so.3
#1  0xb6876528 in IMAP4Protocol::parseRead () from /usr/lib/kde3/kio_imap4.so
#2  0xb6878044 in imapParser::parseLiteralC () from /usr/lib/kde3/kio_imap4.so
#3  0xb688dc2c in imapParser::parseBody () from /usr/lib/kde3/kio_imap4.so
#4  0xb688e78f in imapParser::parseFetch () from /usr/lib/kde3/kio_imap4.so
#5  0xb688f1a5 in imapParser::parseUntagged () from /usr/lib/kde3/kio_imap4.so
#6  0xb688f903 in imapParser::parseLoop () from /usr/lib/kde3/kio_imap4.so
#7  0xb689c5de in IMAP4Protocol::get () from /usr/lib/kde3/kio_imap4.so
#8  0xb7b63a40 in KIO::SlaveBase::dispatch () from /usr/lib/libkio.so.4
#9  0xb68754af in IMAP4Protocol::dispatch () from /usr/lib/kde3/kio_imap4.so
#10 0xb7b4763e in KIO::SlaveBase::dispatchLoop () from /usr/lib/libkio.so.4
#11 0xb688cbee in kdemain () from /usr/lib/kde3/kio_imap4.so

This is extremely reproducible, and it's totally preventing me from using kmail, so if there is anything I can do to help, please let me know!
Comment 4 Arne Schmitz 2005-10-07 09:59:54 UTC
Am Freitag, 7. Oktober 2005 09:03 schrieb Ted Lemon:
> This is extremely reproducible, and it's totally preventing me from using
> kmail, so if there is anything I can do to help, please let me know!


Try the offline IMAP. That works for me.

Arne
Comment 5 Ted Lemon 2005-10-08 08:13:35 UTC
I'm using offline imap.   And in any case, a crash is a crash - a thing to fix, not a thing to ignore in hopes that it will go away.
Comment 6 Björn Ruberg 2009-12-21 19:48:20 UTC
Did it go away?
Comment 7 Myriam Schweingruber 2012-07-08 19:58:29 UTC
No answer for question in comment #6 since 2009. Please feel free to reopen this report if you can reproduce it with Kmail2
Comment 8 Myriam Schweingruber 2012-08-19 12:04:56 UTC
Closing for lack of feedback. Kmail1 is currently unmaintained. Please feel free to reopen this report if you can reproduce it with Kmail2 4.8.5 or later and provide a new backtrace.