Backtrace of the crash...

[New Thread 16384 (LWP 4286)]
0x420d5137 in waitpid () from /lib/libpthread.so.0
#0  0x420d5137 in waitpid () from /lib/libpthread.so.0
#1  0x414f7b1d in KCrash::defaultCrashHandler(int) (sig=11) at kcrash.cpp:246
#2  0x420d3fea in __pthread_sighandler () from /lib/libpthread.so.0
#3  <signal handler called>
#4  0x401d1601 in KMFolderTree::slotFolderExpanded(QListViewItem*) (
    this=0x816fd28, item=0xfffffe00) at kmfoldertree.cpp:1438
#5  0x401d2b1c in KMFolderTree::qt_invoke(int, QUObject*) (this=0x816fd28, 
    _id=-1073754496, _o=0xbfffcdfc) at kmfoldertree.moc:445
#6  0x419714ee in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x816fd28, clist=0x8165c48, o=0xbfffd1e0) at kernel/qobject.cpp:2333
#7  0x41d5d66d in QListView::expanded(QListViewItem*) (this=0x816fd28, 
    t0=0x81fc808) at .moc/debug-shared-mt/moc_qlistview.cpp:545
#8  0x41a7ab0b in QListViewItem::setOpen(bool) (this=0x81fc808, o=true)
    at widgets/qlistview.cpp:1476
#9  0x401cd9e5 in KMFolderTree::addDirectory(KMFolderDir*, KMFolderTreeItem*) (
    this=0x816fd28, fdir=0x813634c, parent=0x0) at kmfoldertree.cpp:632
#10 0x401cd355 in KMFolderTree::reload(bool) (this=0x816fd28, 
    openFolders=false) at kmfoldertree.cpp:510
#11 0x401cdda0 in KMFolderTree::doFolderListChanged() (this=0x816fd28)
    at kmfoldertree.cpp:706
#12 0x401d2a4f in KMFolderTree::qt_invoke(int, QUObject*) (this=0x816fd28, 
    _id=135493408, _o=0x816fd28) at kmfoldertree.moc:439
#13 0x41971628 in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x8136320, clist=0x813dff0, o=0xbfffd480) at kernel/qobject.cpp:2357
#14 0x41971346 in QObject::activate_signal(int) (this=0x8136320, signal=2)
    at kernel/qobject.cpp:2302
#15 0x40258850 in KMFolderMgr::changed() (this=0xfffffe00)
    at kmfoldermgr.moc:130
#16 0x402586d5 in KMFolderMgr::quiet(bool) (this=0x8136320)
    at kmfoldermgr.cpp:499
#17 0x402aed29 in KMFolderImap::slotListResult(QStringList, QStringList, QStringList, KMail::ImapAccountBase::jobData const&) (this=0x8135e18, mSubfolderNames=
        {<QValueList<QString>> = {sh = 0x82b7f18}, <No data fields>}, 
    mSubfolderPaths=
        {<QValueList<QString>> = {sh = 0x8310600}, <No data fields>}, 
    mSubfolderMimeTypes=
        {<QValueList<QString>> = {sh = 0x83105d0}, <No data fields>}, 
    jobData=@0x8136320) at kmfolderimap.cpp:602
#18 0x402b4e9f in KMFolderImap::qt_invoke(int, QUObject*) (this=0x8135e18, 
    _id=-1073752576, _o=0xbfffd620) at kmfolderimap.moc:272
#19 0x419714ee in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x8144f58, clist=0x8204a98, o=0xbfffd6d0) at kernel/qobject.cpp:2333
#20 0x40295fa0 in KMail::ImapAccountBase::receivedFolders(QStringList, QStringList, QStringList, KMail::ImapAccountBase::jobData const&) (this=0x8144f58, t0=)
    at imapaccountbase.moc:164
#21 0x40294c8b in KMail::ImapAccountBase::slotListResult(KIO::Job*) (
    this=0x8144f58, job=0x82028e8) at imapaccountbase.cpp:397
#22 0x4029617c in KMail::ImapAccountBase::qt_invoke(int, QUObject*) (
    this=0x8144f58, _id=6, _o=0x82028e8) at imapaccountbase.moc:185
#23 0x4029cd67 in KMAcctImap::qt_invoke(int, QUObject*) (this=0x8144f58, 
    _id=6, _o=0x82028e8) at kmacctimap.moc:120
#24 0x419714ee in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x82028e8, clist=0x8204468, o=0xbfffd8e0) at kernel/qobject.cpp:2333
#25 0x40f1985f in KIO::Job::result(KIO::Job*) (this=0x82028e8, t0=0xfffffe00)
    at jobclasses.moc:156
#26 0x40f07dac in KIO::Job::emitResult() (this=0x82028e8) at job.cpp:206
#27 0x40f092e6 in KIO::SimpleJob::slotFinished() (this=0x82028e8)
    at job.cpp:530
#28 0x40f0f44d in KIO::ListJob::slotFinished() (this=0x82028e8) at job.cpp:1815
#29 0x40f1c900 in KIO::ListJob::qt_invoke(int, QUObject*) (this=0x82028e8, 
    _id=136325352, _o=0x82028e8) at jobclasses.moc:1370
#30 0x419714ee in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x8208078, clist=0x82ca780, o=0xbfffdbe0) at kernel/qobject.cpp:2333
#31 0x41971346 in QObject::activate_signal(int) (this=0x8208078, signal=6)
    at kernel/qobject.cpp:2302
#32 0x40efafc3 in KIO::SlaveInterface::finished() (this=0xfffffe00)
    at slaveinterface.moc:226
#33 0x40ef9d3b in KIO::SlaveInterface::dispatch(int, QMemArray<char> const&) (
    this=0x8208078, _cmd=104, rawdata=@0x8208078) at slaveinterface.cpp:255
#34 0x40ef954b in KIO::SlaveInterface::dispatch() (this=0x8208078)
    at slaveinterface.cpp:191
#35 0x40ef748d in KIO::Slave::gotInput() (this=0xbfffddf0) at slave.cpp:294
#36 0x40ef8bc8 in KIO::Slave::qt_invoke(int, QUObject*) (this=0xbfffddf0, 
    _id=136347768, _o=0xbfffdf70) at slave.moc:113
#37 0x419714ee in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x8165f30, clist=0x8206d18, o=0xbfffdf70) at kernel/qobject.cpp:2333
#38 0x4197195d in QObject::activate_signal(int, int) (this=0x8165f30, 
    signal=2, param=15) at kernel/qobject.cpp:2426
#39 0x41d4397b in QSocketNotifier::activated(int) (this=0x8165f30, t0=15)
    at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#40 0x41995f7b in QSocketNotifier::event(QEvent*) (this=0x8165f30, 
    e=0xbfffe240) at kernel/qsocketnotifier.cpp:271
#41 0x418ffb95 in QApplication::internalNotify(QObject*, QEvent*) (
    this=0xbffff260, receiver=0x8165f30, e=0xbfffe240)
    at kernel/qapplication.cpp:2582
#42 0x418fedd8 in QApplication::notify(QObject*, QEvent*) (this=0xbffff260, 
    receiver=0x8165f30, e=0xbfffe240) at kernel/qapplication.cpp:2305
#43 0x4146fab9 in KApplication::notify(QObject*, QEvent*) (this=0xbffff260, 
    receiver=0x8165f30, event=0xbfffe240) at kapplication.cpp:509
#44 0x40535bbd in QApplication::sendEvent(QObject*, QEvent*) (
    receiver=0xfffffe00, event=0x0) at qapplication.h:492
#45 0x418eb027 in QEventLoop::activateSocketNotifiers() (this=0x80d8650)
    at kernel/qeventloop_unix.cpp:579
#46 0x4189b468 in QEventLoop::processEvents(unsigned) (this=0x80d8650, flags=4)
    at kernel/qeventloop_x11.cpp:340
#47 0x419190e1 in QEventLoop::enterLoop() (this=0x80d8650)
    at kernel/qeventloop.cpp:198
#48 0x418ffdaf in QApplication::enter_loop() (this=0xbffff260)
    at kernel/qapplication.cpp:2737
#49 0x41b4898c in QDialog::exec() (this=0x82c8ec8) at dialogs/qdialog.cpp:370
#50 0x412c41c1 in createKMessageBox (dialog=0x82c8ec8, icon=Critical, 
    text=@0xbfffe680, strlist=@0xbfffe530, ask=@0x804e914, checkboxReturn=0x0, 
    options=1, details=@0x804e914) at kmessagebox.cpp:284
#51 0x412c294f in KMessageBox::errorWId(unsigned long, QString const&, QString const&, int) (parent_id=50331664, text=@0xfffffe00, caption=@0xbfffe690, 
    options=0) at kmessagebox.cpp:709
#52 0x412c3a2e in KMessageBox::messageBoxWId(unsigned long, KMessageBox::DialogType, QString const&, QString const&, KGuiItem const&, KGuiItem const&, QString const&, int) (parent_id=50331664, type=4294966784, text=@0xbfffe680, 
    caption=@0xbfffe690, buttonYes=@0x0, buttonNo=@0x0, dontShow=@0x804e914, 
    options=50331664) at kmessagebox.cpp:944
#53 0x412c3861 in KMessageBox::messageBox(QWidget*, KMessageBox::DialogType, QString const&, QString const&, KGuiItem const&, KGuiItem const&, int) (
    parent=0xfffffe00, type=4294966784, text=@0xfffffe00, caption=@0xfffffe00, 
    buttonYes=@0xfffffe00, buttonNo=@0xfffffe00, options=-512)
    at kmessagebox.cpp:913
#54 0x40295201 in KMail::ImapAccountBase::slotSlaveError(KIO::Slave*, int, QString const&) (this=0x3000010, aSlave=0x81ff038, errorCode=134539540, 
    errorMsg=@0x82ba538) at imapaccountbase.cpp:481
#55 0x4029507d in KMail::ImapAccountBase::slotSchedulerSlaveError(KIO::Slave*, int, QString const&) (this=0x804e914, aSlave=0x0, errorCode=50331664, 
    errorMsg=@0xfffffe00) at imapaccountbase.cpp:458
#56 0x402962e8 in KMail::ImapAccountBase::qt_invoke(int, QUObject*) (
    this=0x813f408, _id=134539540, _o=0x3000010) at imapaccountbase.moc:192
#57 0x4029cd67 in KMAcctImap::qt_invoke(int, QUObject*) (this=0x813f408, 
    _id=134539540, _o=0x3000010) at kmacctimap.moc:120
#58 0x41971628 in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x8135a18, clist=0x813d9e0, o=0xbfffe7f0) at kernel/qobject.cpp:2357
#59 0x40f02ece in KIO::Scheduler::slaveError(KIO::Slave*, int, QString const&)
    (this=0xbfffe840, t0=0xfffffe00, t1=-512, t2=@0xfffffe00)
    at scheduler.moc:153
#60 0x40f02312 in KIO::Scheduler::slotSlaveError(int, QString const&) (
    this=0x3000010, errorNr=-512, errorMsg=@0xfffffe00) at scheduler.cpp:780
#61 0x40f0306a in KIO::Scheduler::qt_invoke(int, QUObject*) (this=0x8135a18, 
    _id=-1073747904, _o=0x3000010) at scheduler.moc:164
#62 0x419714ee in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x81ff038, clist=0x82070b0, o=0xbfffe950) at kernel/qobject.cpp:2333
#63 0x40efaf2c in KIO::SlaveInterface::error(int, QString const&) (
    this=0x81ff038, t0=-512, t1=@0xfffffe00) at slaveinterface.moc:214
#64 0x40ef9cf3 in KIO::SlaveInterface::dispatch(int, QMemArray<char> const&) (
    this=0x81ff038, _cmd=102, rawdata=@0xbfffe98c) at slaveinterface.cpp:292
#65 0x40ef954b in KIO::SlaveInterface::dispatch() (this=0x81ff038)
    at slaveinterface.cpp:191
#66 0x40ef748d in KIO::Slave::gotInput() (this=0xbfffeb70) at slave.cpp:294
#67 0x40ef8bc8 in KIO::Slave::qt_invoke(int, QUObject*) (this=0xbfffeb70, 
    _id=136310840, _o=0xbfffecf0) at slave.moc:113
#68 0x419714ee in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x81faad0, clist=0x81ff998, o=0xbfffecf0) at kernel/qobject.cpp:2333
#69 0x4197195d in QObject::activate_signal(int, int) (this=0x81faad0, 
    signal=2, param=14) at kernel/qobject.cpp:2426
#70 0x41d4397b in QSocketNotifier::activated(int) (this=0x81faad0, t0=14)
    at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#71 0x41995f7b in QSocketNotifier::event(QEvent*) (this=0x81faad0, 
    e=0xbfffefc0) at kernel/qsocketnotifier.cpp:271
#72 0x418ffb95 in QApplication::internalNotify(QObject*, QEvent*) (
    this=0xbffff260, receiver=0x81faad0, e=0xbfffefc0)
    at kernel/qapplication.cpp:2582
#73 0x418fedd8 in QApplication::notify(QObject*, QEvent*) (this=0xbffff260, 
    receiver=0x81faad0, e=0xbfffefc0) at kernel/qapplication.cpp:2305
#74 0x4146fab9 in KApplication::notify(QObject*, QEvent*) (this=0xbffff260, 
    receiver=0x81faad0, event=0xbfffefc0) at kapplication.cpp:509
#75 0x40535bbd in QApplication::sendEvent(QObject*, QEvent*) (
    receiver=0xfffffe00, event=0x0) at qapplication.h:492
#76 0x418eb027 in QEventLoop::activateSocketNotifiers() (this=0x80d8650)
    at kernel/qeventloop_unix.cpp:579
#77 0x4189b468 in QEventLoop::processEvents(unsigned) (this=0x80d8650, flags=4)
    at kernel/qeventloop_x11.cpp:340
#78 0x419190e1 in QEventLoop::enterLoop() (this=0x80d8650)
    at kernel/qeventloop.cpp:198
#79 0x41918ffa in QEventLoop::exec() (this=0x80d8650)
    at kernel/qeventloop.cpp:145
#80 0x418ffd53 in QApplication::exec() (this=0xbffff260)
    at kernel/qapplication.cpp:2705
#81 0x0804c235 in main (argc=-512, argv=0xfffffe00) at main.cpp:212
#82 0x4222f90c in __libc_start_main () from /lib/libc.so.6

I couldn't reproduce exactly the same case in a valgrind session, I may have something interresting but I'm not sure it is the same crash, tell me if you want me to attached that valgrind log...

Yes, please attach the log. Could you also please try to reproduce this with current cvs? I'm unable to, so maybe this is now fixed. Thanks a lot.

I installed 3.2_rc1 and tried to reproduce all that.
There are still problems, I got lots of crashes, but all looked different and happened at different time ... it is even harder because kmail won't start twice with the same behaviour after a crash so it's very difficult to start in a known situation.

I don't think it's worth posting many backtraces, all different and none I can reproduce, isn't it ?

But all this is maybe due to a problem with my imap server, that problem made me report bug 70463.

I don't understand what happens with that server. That server supports STARTTLS (got it from sniffing a kmail connection to it), but kmail always reports "Start TLS failed" although it tries to STARTTLS on port 143. the server is mailbox.epfl.ch, maybe you could test that one ?

here is a piece of talk between kmail and the server (tcp port 143)
* OK Messaging Multiplexor (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)).
2 CAPABILITY.
* CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS CHILDREN LANGUAGE XSENDER X-NETSCAPE XSERVERINFO AUTH=PLAIN STARTTLS.
2 OK CAPABILITY completed.
3 STARTTLS.
3 OK STARTTLS completed.

and then some un(human)readable bytes, and the error

How may I help you now ?

Do you still get that crash with the release version (3.2 rc1 or higher)?

with 3.2-rc1 : I've got lots of similar crashes when playing with that account. But as I said on comment #4, I can produce a lot of crashes but the crash happens in different situation, I can't find a way to reproduce it 100%.

That's why I put comment #5, I was hoping you could try to connect to that server and get the same kind of crashes I've got...

Subject: Re:  crash when hitting cancel when asked for a password

Arnaud Burlet sagte:
> with 3.2-rc1 : I've got lots of similar crashes when playing with that
> account. But as I said on comment #4, I can produce a lot of crashes but
> the crash happens in different situation, I can't find a way to reproduce
> it 100%.
>
> That's why I put comment #5, I was hoping you could try to connect to that
> server and get the same kind of crashes I've got...

I can't really test a server without login and password.
Can you post at least one backtrace? Make sure you compiled kmail with
--enable-debug=yes

I can have the "Starting TLS failed" error using a random username+password.

about a backtrace : I obtained that one entering a random password and clicking OK the first time kmails asks for the pass ...

[New Thread 16384 (LWP 4143)]
0x420e55b8 in waitpid () from /lib/libpthread.so.0
#0  0x420e55b8 in waitpid () from /lib/libpthread.so.0
#1  0x415c00ac in __JCR_LIST__ () from /usr/kde/3.2/lib/libkdecore.so.4
#2  0x420e4383 in __pthread_sighandler () from /lib/libpthread.so.0
#3  <signal handler called>
#4  0x401d4228 in KMFolderTree::readIsListViewItemOpen(KMFolderTreeItem*) (
    this=0x817c998, fti=0x1034) at kmfoldertree.cpp:1144
#5  0x401d17f4 in KMFolderTree::addDirectory(KMFolderDir*, KMFolderTreeItem*) (
    this=0x817c998, fdir=0x813304c, parent=0x0) at kmfoldertree.cpp:645
#6  0x401d1145 in KMFolderTree::reload(bool) (this=0x817c998, 
    openFolders=false) at kmfoldertree.cpp:517
#7  0x401d5d13 in KMFolderTree::toggleColumn(int, bool) (this=0x817c998, 
    column=1077683816, openFolders=104) at kmfoldertree.cpp:1564
#8  0x40336877 in KMMainWidget::readConfig() (this=0x8148668)
    at kmmainwidget.cpp:304
#9  0x40335698 in KMMainWidget (this=0x8148668, parent=0xfffffe00, 
    name=0xfffffe00 <Address 0xfffffe00 out of bounds>, 
    actionCollection=0xfffffe00, config=0xfffffe00) at kmmainwidget.cpp:122
#10 0x40175d29 in KMMainWin (this=0x805b038) at kmmainwin.cpp:23
#11 0x402d3613 in KMKernel::openReader() (this=0xbfffee60) at kmkernel.cpp:287
#12 0x402d8358 in KMKernel::action(bool, bool, QString const&, QString const&, QString const&, QString const&, QString const&, KURL const&, KURL::List const&)
    (this=0xbfffee60, check=false, to=@0xfffffe00, cc=@0xfffffe00, 
    bcc=@0xfffffe00, subj=@0xfffffe00, body=@0xfffffe00, 
    messageFile=@0xfffffe00, attachURLs=@0xfffffe00) at kmkernel.cpp:1399
#13 0x402d2f87 in KMKernel::handleCommandLine(bool) (this=0xfffffe00, 
    noArgsOpensReader=true) at kmkernel.cpp:245
#14 0x0804a0c0 in KMailApplication::newInstance() (this=0xfffffe00)
    at main.cpp:62
#15 0x41523b9d in KUniqueApplication::processDelayed() (this=0xbfffef50)
    at kuniqueapplication.cpp:398
#16 0x41523f98 in KUniqueApplication::qt_invoke(int, QUObject*) (
    this=0xbfffef50, _id=18, _o=0xfffffe00) at kuniqueapplication.moc:86
#17 0x419814ee in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x8123248, clist=0x8123470, o=0xbfffe9b0) at kernel/qobject.cpp:2333
#18 0x41d52b4e in QSignal::signal(QVariant const&) (this=0x8123248, 
    t0=@0x8123270) at .moc/debug-shared-mt/moc_qsignal.cpp:100
#19 0x419a31e6 in QSignal::activate() (this=0x8123248)
    at kernel/qsignal.cpp:204
#20 0x419ace08 in QSingleShotTimer::event(QEvent*) (this=0x8123220)
    at kernel/qtimer.cpp:277
#21 0x4190fb95 in QApplication::internalNotify(QObject*, QEvent*) (
    this=0xbfffef50, receiver=0x8123220, e=0xbfffec80)
    at kernel/qapplication.cpp:2582
#22 0x4190edd8 in QApplication::notify(QObject*, QEvent*) (this=0xbfffef50, 
    receiver=0x8123220, e=0xbfffec80) at kernel/qapplication.cpp:2305
#23 0x4147cd55 in KApplication::notify(QObject*, QEvent*) (this=0xbfffef50, 
    receiver=0x8123220, event=0xbfffec80) at kapplication.cpp:505
#24 0x4053b35d in QApplication::sendEvent(QObject*, QEvent*) (
    receiver=0xfffffe00, event=0x0) at qapplication.h:492
#25 0x418faecb in QEventLoop::activateTimers() (this=0x80d59e0)
    at kernel/qeventloop_unix.cpp:557
#26 0x418ab484 in QEventLoop::processEvents(unsigned) (this=0x80d59e0, flags=4)
    at kernel/qeventloop_x11.cpp:346
#27 0x419290e1 in QEventLoop::enterLoop() (this=0x80d59e0)
    at kernel/qeventloop.cpp:198
#28 0x41928ffa in QEventLoop::exec() (this=0x80d59e0)
    at kernel/qeventloop.cpp:145
#29 0x4190fd53 in QApplication::exec() (this=0xbfffef50)
    at kernel/qapplication.cpp:2705
#30 0x0804a235 in main (argc=-512, argv=0xfffffe00) at main.cpp:115
#31 0x4223edcc in __libc_start_main () from /lib/libc.so.6

I'll attach 3 other backtraces

Created attachment 4360 [details]
Backtrace of a crash

I obtained that one pressing cancel when kmail prompted for the password, at
the 3rd time kmail crashed

Created attachment 4361 [details]
backtrace of a crash

start kmail, it asks for a password. I type a random password but then I press
cancel and kmal crashed

Created attachment 4362 [details]
backtrace of a crash

When kmail prompts the first time for a password, I entered a random one,
pressed ok and kmail crashed

Subject: Re:  crash when hitting cancel when asked for a password

On Monday 26 January 2004 17:14, Arnaud Burlet wrote:
> start kmail, it asks for a password. I type a random password but then I
> press cancel and kmal crashed

Looks like there is something pretty broken with your account. Does it help to 
recreate the account?


Carsten

Yes, I've already done that 2 days ago. To be sure I just did it now :
start kontact
kmail -> remove the account
quit kontact
start kontact
kmail -> create the account
...
quit kontact
start kontact --> I could reproduce the crash described in comment #11 with a similar backtrace

Do you encounter these crashes when you start kmail standalone and not within kontact?

My last try (described in #14) was within kontact
all the other were using kmail standalone

*** This bug has been marked as a duplicate of 73667 ***