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

List:       kmail-devel
Subject:    Re: [Bug 48307] kmail crashed after changing from an imap folder busy with copying to a local local
From:       Stephan Kulow <coolo () kde ! org>
Date:       2002-10-14 14:54:54
[Download RAW message or body]

Am Monday 14 October 2002 15:57 schrieb Carsten Burghardt:
>  Stephan Kulow wrote:
> > ------- You are receiving this mail because: -------
> > You are the assignee for the bug, or are watching the assignee.
> >
> > http://bugs.kde.org/show_bug.cgi?id=48307
> >
> >
> >
> >
> > ------- Additional Comments From coolo@kde.org  2002-10-14 13:16
> > ------- Subject: Re:  kmail crashed after changing from an imap
> > folder busy with copying to a local local folder
> >
> > Am Monday 14 October 2002 00:37 schrieb
> >
> > matze@stud.fbi.fh-darmstadt.de:
> >> ------- You are receiving this mail because: -------
> >> You are the assignee for the bug, or are watching the assignee.
> >>
> >> http://bugs.kde.org/show_bug.cgi?id=48307
> >>
> >>
> >>
> >>
> >> ------- Additional Comments From matze@stud.fbi.fh-darmstadt.de
> >> 2002-10-14 00:37 ------- I can reproduce this bug as eva
> >> described easily. The backtrace I get is about the same, however
> >> it crashes in
> >> KMMsgBase::getMsgSerNum():
> >>
> >> #0  0x41618079 in wait4 () from /lib/libc.so.6
> >> #1  0x41690944 in __DTOR_END__ () from /lib/libc.so.6
> >> #2  0x414b2177 in waitpid () from /lib/libpthread.so.0
> >> #3  0x40c3c53c in KCrash::defaultCrashHandler (sig=11) at
> >> kcrash.cpp:235 #4  0x414afbc4 in pthread_sighandler () from
> >> /lib/libpthread.so.0 #5  <signal handler called>
> >> #6  0x81ab28a in KMMsgBase::getMsgSerNum (this=0x874b510) at
> >> kmmsgbase.cpp:774 #7  0x81cad8a in KMFolderImap::addMsgQuiet
> >> (this=0x8390818, aMsg=0x874b510) at kmfolderimap.cpp:168
> >> #8  0x81ea619 in KMFolderImap::qt_invoke (this=0x8390818, _id=4,
> >> _o=0xbfffe904)
> >>     at kmfolderimap.moc:453
> >> #9  0x40f71e44 in QObject::activate_signal ()
> >>    from /usr/lib/qt3/lib/libqt-mt.so.3
> >> #10 0x81e9fef in KMImapJob::messageStored (this=0x8703060,
> >> t0=0x874b510)
> >>     at kmfolderimap.moc:149
> >> #11 0x81dfdd2 in KMImapJob::slotPutMessageResult
> >> (this=0x8703060,
> >>     job=0x8672e98) at kmfolderimap.cpp:1190
> >>
> >> Just to make it clear how to reproduce: Copy some mails from one
> >> imap server to another imap server, and switch to a local folder
> >> *while it's still copying*.
> >
> > Can you download valgrind 1.0.3 and try that action with a kmail
> > running under valgrind?
>
> You don't need that. It simly crashes because the destination folder
> is closed before the message reaches it. I'll set the
> contentState-flag of the imap-folder to imapInProgress when such a
> copy/move is in progress and then defer the closing of the folder.

Carsten - you should ask the valgrind question _more_ often. When you
use valgrind kmail takes ten times longer (with a valid excuse), so you can
find only a tenth the number of bugs you would find if used without valgrind.
Of course this is based on the assumption that all known bugs are fixed at
that point :)

Greetings, Stephan

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail
[prev in list] [next in list] [prev in thread] [next in thread]