Summary: | kmail crashes when opening a (specific) IMAP inbox | ||
---|---|---|---|
Product: | [Applications] kmail | Reporter: | Bernhard Rosenkraenzer <bero> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, christophe, mail |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Bernhard Rosenkraenzer
2008-12-27 02:29:59 UTC
Unfortunately, your backtrace is useless without debug symbols. Please recompile kdepimlibs and kdepim with the debug symbols to provide a better bt. More informations on this page : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports The backtrace is from kdelibs, kdepimlibs and kdepim built with debug info. Looks like something is corrupting the stack. Triggering this crash in kmail -nofork started from within gdb triggers very strange behavior as well: [arklinux@localhost ~]$ gdb kmail GNU gdb Ark Linux (6.8-1ark) Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... (gdb) set args -nofork (gdb) run Starting program: /usr/bin/kmail -nofork Object::connect: No such signal OrgFreedesktopAkonadiAgentManagerInterface::agentInstanceOnlineChanged(QString,bool) "/usr/bin/kmail(4363)" Error in thread 3083548416 : "org.freedesktop.DBus.Error.UnknownObject - No such object path '/org/soprano/Server'" "/usr/bin/kmail(4363)" Error in thread 3083548416 : "QLocalSocket::connectToServer: Invalid name" kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path [New LWP 4415] kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderIndex::updateIndexStreamPtr: utime( "/home/arklinux/.kde/share/apps/kmail/imap/.1599001121.directory/.cron-output.index.ids" , 0) failed (KMMsgDict::getFolderIdsLocation( *this )) kmail(4363) KMFolderIndex::updateIndexStreamPtr: utime( "/home/arklinux/.kde/share/apps/kmail/imap/.1599001121.directory/.cron-output.index.ids" , 0) failed (KMMsgDict::getFolderIdsLocation( *this )) kmail(4363) KMFolderImap::setImapPath: ignoring empty path [LWP 4415 exited] [New process 4363] linux-nat.c:1152: internal-error: linux_nat_resume: Assertion `lp != NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) Please answer y or n. linux-nat.c:1152: internal-error: linux_nat_resume: Assertion `lp != NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) n linux-nat.c:1152: internal-error: linux_nat_resume: Assertion `lp != NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. This may be duplicated/related to bug 180554 (same situation and similar backtrace (at least the same function before crashing)) *** This bug has been marked as a duplicate of bug 179765 *** |