| Summary: | stochastic crash with signal 11 (SIGSEGV) | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | alason <spam.me> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | mboquien, Regnaron |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
alason
2008-11-14 01:51:45 UTC
Hello, Thank you for the report. Unfortunately it appears the backtrace is not usable due to missing symbols. Please follow the instructions provided on this page http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and resubmit an updated backtrace. Thank you. (In reply to comment #1) > Hello, > > Thank you for the report. Unfortunately it appears the backtrace is not usable > due to missing symbols. Please follow the instructions provided on this page > http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports > and resubmit an updated backtrace. > > Thank you. > Thanks for your fast reply. I hope I have now the usable backtrace: Application: Kontact (kontact), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb4ce86c0 (LWP 30087)] [KCrash handler] #6 Akregator::FeedList::findByID (this=0x0, id=501923572) at /build/buildd/kdepim-4.1.2/akregator/src/feedlist.cpp:390 #7 0xb1151079 in Akregator::ExpireItemsCommand::Private::createDeleteJobs ( this=0xa099b30) at /build/buildd/kdepim-4.1.2/akregator/src/expireitemscommand.cpp:89 #8 0xb11511ae in Akregator::ExpireItemsCommand::qt_metacall (this=0xa098c10, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfbb7c18) at /build/buildd/kdepim-4.1.2/obj-i486-linux-gnu/akregator/src/expireitemscommand.moc:67 #9 0xb77cba60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #10 0xb77cc7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb77d1db7 in ?? () from /usr/lib/libQtCore.so.4 #12 0xb77d1edc in ?? () from /usr/lib/libQtCore.so.4 #13 0xb77c653f in QObject::event () from /usr/lib/libQtCore.so.4 #14 0xb6ea78ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #15 0xb6eaf76e in QApplication::notify () from /usr/lib/libQtGui.so.4 #16 0xb7c8572d in KApplication::notify (this=0xbfbb8358, receiver=0xa0952e8, event=0xbfbb80ac) at /build/buildd/kde4libs-4.1.2/kdeui/kernel/kapplication.cpp:311 #17 0xb77b6e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #18 0xb77e4d81 in ?? () from /usr/lib/libQtCore.so.4 #19 0xb77e1520 in ?? () from /usr/lib/libQtCore.so.4 #20 0xb55d36f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #21 0xb55d6da3 in ?? () from /usr/lib/libglib-2.0.so.0 #22 0xb55d6f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #23 0xb77e1478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #24 0xb6f41ee5 in ?? () from /usr/lib/libQtGui.so.4 #25 0xb77b552a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #26 0xb77b56ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #27 0xb77b7da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #28 0xb6ea7767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #29 0x0804bf52 in main (argc=3, argv=0xbfbb8654) at /build/buildd/kdepim-4.1.2/kontact/src/main.cpp:218 #0 0xb7fb8430 in __kernel_vsyscall () Hi! Jep, the new backtrace is better, thanks. Actually it seems like you ran into the same problem described in bug #164265 which should be fixed in KDE-4.1.3 *** This bug has been marked as a duplicate of bug 164265 *** |