| Summary: | Crash after reading index with serialnumber == 0 | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Gualter Barbas Baptista <gualter> |
| Component: | index | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | gandhiano, gualter, jtamate, j_kolberg11, robin.rosenberg, roland |
| Priority: | NOR | Keywords: | triaged |
| Version: | SVN trunk (KDE 4) | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | kdepim 4.6 | |
| Sentry Crash Report: | |||
|
Description
Gualter Barbas Baptista
2008-11-11 14:19:00 UTC
Hi Gualter, unfortunately, the backtrace you posted is not much useful. You can get a more detailed one by following the instructions on the following page: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports Thanks! Ok, sorry for the useless backtrace. Here is a proper one:
Application: KMail (kmail), signal SIGABRT
[Thread debugging using libthread_db enabled]
[New Thread 0x7f367c1c46f0 (LWP 19444)]
[KCrash handler]
#5 0x00007f36791f7ed5 in raise () from /lib/libc.so.6
#6 0x00007f36791f93f3 in abort () from /lib/libc.so.6
#7 0x00007f367a5f25a5 in qt_message_output (msgType=QtFatalMsg,
buf=<value optimized out>) at global/qglobal.cpp:2102
#8 0x00007f367a5f26e7 in qFatal (msg=<value optimized out>)
at global/qglobal.cpp:2303
#9 0x00007f367b98ba88 in KMMsgDict::readFolderIds (this=0x1169d20,
storage=@0x12eb5a0) at /tmp/buildd/kdepim-4.1.3/kmail/kmmsgdict.cpp:476
#10 0x00007f367b991120 in FolderStorage::readFolderIdsFile (this=0x12eb5a0)
at /tmp/buildd/kdepim-4.1.3/kmail/folderstorage.cpp:1000
#11 0x00007f367b9689d1 in KMFolder (this=0x1309290, aParent=0x14b9390,
aFolderName=@0x7fff84312670, aFolderType=<value optimized out>,
withIndex=<value optimized out>, exportedSernums=<value optimized out>)
at /tmp/buildd/kdepim-4.1.3/kmail/kmfolder.cpp:146
#12 0x00007f367b9b3813 in KMFolderDir::reload (this=0x14b9390)
at /tmp/buildd/kdepim-4.1.3/kmail/kmfolderdir.cpp:288
#13 0x00007f367b9b3570 in KMFolderDir::reload (this=0x13c4a18)
at /tmp/buildd/kdepim-4.1.3/kmail/kmfolderdir.cpp:299
#14 0x00007f367b9b80b8 in KMFolderMgr::setBasePath (this=0x13c4a00,
aBasePath=@0x7fff84313050)
at /tmp/buildd/kdepim-4.1.3/kmail/kmfoldermgr.cpp:163
#15 0x00007f367b9b846f in KMFolderMgr (this=0x13c4a00,
aBasePath=@0x7fff84313050, dirType=KMDImapDir)
at /tmp/buildd/kdepim-4.1.3/kmail/kmfoldermgr.cpp:44
#16 0x00007f367ba978cd in KMKernel::init (this=0x7fff843131d0)
at /tmp/buildd/kdepim-4.1.3/kmail/kmkernel.cpp:1419
#17 0x0000000000402f43 in main (argc=<value optimized out>,
argv=<value optimized out>) at /tmp/buildd/kdepim-4.1.3/kmail/main.cpp:128
#0 0x00007f3679263fc0 in __nanosleep_nocancel () from /lib/libc.so.6
I think the Q_ASSERT (msn != 0) should be Q_ASSERT(msn==0) in kmail/kmmsgdict.cpp:476. > I think the Q_ASSERT (msn != 0) should be Q_ASSERT(msn==0) in kmail/kmmsgdict.cpp:476.
No, that assert is correct, serial number == zero is not allowed, as the comment explains.
SVN commit 886618 by tmcguire: Serial numbers are unsigned long, not quint32. This is the only possible reason I could imagine why it goes wrong like in bug 174866. It would also explain why I never could reproduce this with my 32 bit CPU. Maybe this even is the real root cause for the serial number == 0 bug?? In any case, I hope other places get the type right. BUG: 174866 M +1 -1 kmmsgdict.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=886618 Reopening, I've just revert this as it was causing additional crashes on 64 bit systems. *** Bug 175207 has been marked as a duplicate of this bug. *** I had this issue happening on another computer (also 64 bit), which has a similar configuration. I suspect it has to do with IMAP accounts. Kmail suddenly stopped starting after a crash. I was searching into the kmail share folder and found out some suspect files. I deleted them and after this, it was again working normally. The files were: ~/.kde4/share/apps/kmail/: unfiltered.13219272 unfiltered.1395695691 unfiltered.378008110 ~/.kde4/share/apps/kmail/imap/: 13219272 1395695691 378008110 The ones inside imap have 0 bytes. The unfiltered ones only contain: unfiltered= And nothing else. Hope this helps to fix the issue. And, i The error is recurrent, also on KDE 4.2.0/Kmail 1.11.0. I cannot start Kmail or Kontact after a crash. The crashes are quite frequently happen when I delete messages from the IMAP server, so this is quite an annoying bug. Also, sometimes deleting the files I mentioned above does not work, as Kmail starts, but crashes immediately after. The only way to solve is to delete the whole IMAP tree (one of them, which is the main account with quite a lot of e-mails and folders) at .kde4/share/apps/kmail/imap/.xxxxxxxx.directory Both times this happened to me, I was moving a folder after having read some email in the inbox. The one time my inbox was still there after this error, the message I read prior to moving the folder was marked as unread. Threads are what you get when you don't get a real operating system to work with. Hasn’t happend to me with KDEPIM 4.6 beta 5 Shouldn't happen anymore with the akonadi-pop3 resource. Fixed in kdepim 4.6 (In reply to comment #12) > Shouldn't happen anymore with the akonadi-pop3 resource. corr: Shouldn't happen anymore with the akonadi* resources. |