[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 93965] newimap "Unexpected Program Termination"
From:       Nils Ohlmeier <kde () ohlmeier ! org>
Date:       2004-12-30 18:51:32
Message-ID: 20041230185132.11732.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
        
http://bugs.kde.org/show_bug.cgi?id=93965        




------- Additional Comments From kde ohlmeier org  2004-12-30 19:51 -------
In advance: I upgraded to 3.3.2 but the problem still persits.

I tried my best but unfortunately I get so many unresolved frames in gdb that I fear \
the backtrace is not really usefull:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 27384)]
0x4690674f in QGDict::hashKeyString () from /usr/qt/3/lib/libqt-mt.so.3
(gdb) where
#0  0x4690674f in QGDict::hashKeyString () from /usr/qt/3/lib/libqt-mt.so.3
#1  0x4690725c in QGDict::look_string () from /usr/qt/3/lib/libqt-mt.so.3
#2  0x407bc3d6 in QDict<QString>::insert (this=0x0, k= 0x0, d=0x0) at qdict.h:65
#3  0x4099f307 in mimeHeader::addParameter () from \
/usr/kde/3.3/lib/kde3/kio_newimap4.so #4  0xbfffdeb0 in ?? ()
#5  0xbfffdf20 in ?? ()
#6  0x08155a38 in ?? ()
#7  0x00000000 in ?? ()
#8  0x08155a48 in ?? ()
#9  0x0815673f in ?? ()
#10 0xbfffde88 in ?? ()
#11 0x468f5f8a in QCString::~QCString () from /usr/qt/3/lib/libqt-mt.so.3
Previous frame inner to this frame (corrupt stack?)

Output on the console looks like this:

kio_imap: IMAP4::get -  finished
kmail: ImapJob::slotGetMessageResult - retrieved part 1
kmail: KMMessage::updateBodyPart 1
kmail: ISubject::notify 1
kmail: KMReaderWin::update - message
kmail: parseMsg(KMMessage* aMsg == aMsg )
kmail:
        partNode::partNode()      explicitType == DwMime::kTypeUnknown
kmail:
kmail:
        partNode::partNode()      explicitType == DwMime::kTypeUnknown
kmail:
kmail: + Multipart/Mixed
kmail:  + Text/Plain
kmail:  + Message/Rfc822
kmail:       Inserting one item into MimePartTree
kmail:                 Content-Type: Multipart/Mixed
kmail:       Inserting one item into MimePartTree
kmail:                 Content-Type: MESSAGE/RFC822
kmail:       Inserting one item into MimePartTree
kmail:                 Content-Type: TEXT/PLAIN
kmail: partNode::findType() is looking at Multipart/Mixed
kmail: partNode::findType() is looking at Text/Plain
kmail: partNode::findType() is looking at Message/Rfc822
kmail: final presence: ''
kmail: ObjectTreeParser::parseObjectTree( node OK, showOnlyOneMimePart: FALSE )
kmail: ObjectTreeParser::parseObjectTree( node OK, showOnlyOneMimePart: FALSE )
kmail:
----->  Initially processing data of embedded RfC 822 message
kmail:
kmail:
----->  Store RfC 822 message header "From: "
kmail:
kmail: final presence: ''
kmail: copy parts
kmail:
     ----->  Inserting items into MimePartTree
kmail:
kmail:       Inserting one item into MimePartTree
kmail:                 Content-Type: text/plain
kmail:
     <-----  Finished inserting items into MimePartTree
kmail:
kmail:
     ----->  Now parsing the MimePartTree
kmail:
kmail: ObjectTreeParser::parseObjectTree( node OK, showOnlyOneMimePart: FALSE )
kmail:
     <-----  Finished parsing the MimePartTree in insertAndParseNewChildNode()
kmail:
kmail: KMReaderWin  -  finished parsing and displaying of message.
kio_imap: IMAP4::dispatch - command=67
kio_imap: IMAP4::get -  newimap://ohlmeini%40intern.snom.de merenge intern snom \
                de:143/INBOX/;UID=779;SECTION=BODY PEEK[2 MIME]
kio_imap: URL: box= INBOX, section= BODY.PEEK[2.MIME], type= , uid= 779, validity=
kio_imap: IMAP4::parseURL: box INBOX
kio_imap: IMAP4::parseURL - return 5
kio_imap: IMAP4Protocol::assureBox - reusing box
kio_imap: mimeHeader::parseHeader - starting parsing

So it seems always to fail when trying to parse a header.

Intersting was, that when I allready had attached gdb to the IMAP process and then \
opened the mailbox with one of the problematic messages as allready selected message, \
it did not failed, like it did when I moved from one message to another and hitted a \
problematic one.

As a developer I'm familiar with gdb and could try to track it down on my own. But I \
guess you would be faster. Would you prefer to get the problematic messages (which \
probably does not guarantee that you can reproduce the problem), or should I try to \
debug it (maybe with your help)?


[prev in list] [next in list] [prev in thread] [next in thread]