Bug 174287 - sigsegv while trying to access IMAP folder on server
Summary: sigsegv while trying to access IMAP folder on server
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2008-11-04 18:50 UTC by Marco Walther
Modified: 2009-03-19 00:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Walther 2008-11-04 18:50:54 UTC
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages

I just tried to access an folder on my IMAP server:-(

Application: KMail (kmail), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb41126c0 (LWP 14583)]
[KCrash handler]
#6  0xb702510f in ?? () from /usr/lib/libQtCore.so.4
#7  0xb702516b in ?? () from /usr/lib/libQtCore.so.4
#8  0xb7024fec in QObject::~QObject () from /usr/lib/libQtCore.so.4
#9  0xb7b9404c in ?? () from /usr/lib/libkmailprivate.so.4
#10 0xb7ba1262 in ?? () from /usr/lib/libkmailprivate.so.4
#11 0xb701bdec in qDeleteInEventHandler () from /usr/lib/libQtCore.so.4
#12 0xb701d7a3 in QObject::event () from /usr/lib/libQtCore.so.4
#13 0xb66fe8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#14 0xb670676e in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0xb74dc72d in KApplication::notify (this=0xbfd2e098, receiver=0xab5cd20, 
    event=0xb2a6bc0)
    at /build/buildd/kde4libs-4.1.2/kdeui/kernel/kapplication.cpp:311
#16 0xb700de61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#17 0xb700eae5 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#18 0xb700ecdd in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#19 0xb703882f in ?? () from /usr/lib/libQtCore.so.4
#20 0xb4a946f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0xb4a97da3 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0xb4a97f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0xb7038478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#24 0xb6798ee5 in ?? () from /usr/lib/libQtGui.so.4
#25 0xb700c52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#26 0xb700c6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#27 0xb700eda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#28 0xb66fe767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#29 0x0804a6c0 in _start ()
#0  0xb7f2e430 in __kernel_vsyscall ()
Comment 1 Jaime Torres 2008-11-12 10:23:51 UTC
Hi,

unfortunately, the backtrace you posted is not very useful. 
You can read in:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
further instructions on how to get a more detailed one.
Thank you.
Comment 2 George Goldberg 2008-12-18 12:27:57 UTC
Unfortunately, without a better backtrace as explained by the link in comment #1, it is not possible for this crash to be investigated effectively. I am closing the report, but please feel free to reopen it if you can provide more information or a better backtrace.