Bug 137868 - Knode dies with SIGSEGV error dialog
Summary: Knode dies with SIGSEGV error dialog
Status: RESOLVED BACKTRACE
Alias: None
Product: knode
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-25 18:50 UTC by Grunt
Modified: 2009-10-02 03:19 UTC (History)
1 user (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 Grunt 2006-11-25 18:50:53 UTC
Version:           0.10.1 (using KDE KDE 3.5.1)
Installed from:    SuSE RPMs
Compiler:          gcc 4.1.0 
OS:                Linux

On both Gentoo and OpenSUSE 10.1 Knode dies with the sigsegv (see below).  It does at random intervals but it appears the system has to run a while before it happens.  Let me know if I can do anything to get more information.

Backtrace:

System configuration startup check disabled.

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1242413392 (LWP 5091)]
[New Thread -1247831136 (LWP 5092)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb727cc44 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0xb727da11 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0xb79258e3 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#9  0xb7271884 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb722c644 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0xb7293a78 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0xb729390e in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0xb727c7ff in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x0804ed5a in ?? ()
#15 0xbfe12bdc in ?? ()
#16 0xbfe12cf4 in ?? ()
#17 0x00000001 in ?? ()
#18 0x00000000 in ?? ()
Comment 1 Bram Schoenmakers 2006-11-25 19:02:37 UTC
We cannot do much with the current backtrace. Please provide a more detailed one, which is easier to retrieve on Gentoo. Install the kdepim (or knode) package with the 'debug' useflag and make sure the FEATURES="nostrip" is in your make.conf.
Comment 2 Grunt 2006-11-25 19:09:08 UTC
I've moved to OpenSuse 10.1 now.  Is there a way to provide more debugging info under this platform.  I notice there is a kde-pim debug info rpm available - I assume installing this would give me what you need.


kdepim3-debuginfo - Personal Information Manager Software for KDE


This package contains Kontact and the stand-alone applications for personal information management. Kontact--personal information manager 
KMail--mail client 
KOrganizer--calendar and scheduling program 
KNode--news reader 
Kleopatra and KWatchGnuPG--certification manager 
Various wizards to connect to groupware servers 
Comment 3 Grunt 2006-12-09 01:56:52 UTC
I installed with the knode-debugging in OpenSuse 10.1 and got this.  If this doesn't work let me know what I need to do to get you the data you need.


System configuration startup check disabled.

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1243167056 (LWP 3621)]
[New Thread -1248592992 (LWP 3677)]
[KCrash handler]
#6  0xb7537c3d in QGList::unlink () from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0xb7537ef1 in QGList::removeRef () from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0xb7216e20 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0xb71d1874 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb7239368 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0xb72391fe in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0xb72220ff in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0x0804ed5a in ?? ()
#14 0xbfc71a0c in ?? ()
#15 0xbfc71b24 in ?? ()
#16 0x00000001 in ?? ()
#17 0x00000000 in ?? ()
Comment 4 Bram Schoenmakers 2007-02-03 16:06:14 UTC
You could try to install kdelibs debug and the debug packages of all kdepim components. The backtrace still does not look useful unfortunately.
Comment 5 Grunt 2007-02-03 16:52:30 UTC
Okay.  I'll do that.

On Saturday 03 February 2007 10:06, Bram Schoenmakers wrote:
[bugs.kde.org quoted mail]
Comment 6 Grunt 2007-02-05 03:16:33 UTC
Done.  I'll send you info when I get it.  I did kdepim first.

On Saturday 03 February 2007 10:06, Bram Schoenmakers wrote:
[bugs.kde.org quoted mail]
Comment 7 Grunt 2007-02-15 01:47:24 UTC
I've added the debug for kde-pim.  With OpenSuse 10.1 this should get all the kdepim components. If this isn't good I'll do the kdelibs.

System configuration startup check disabled.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1242937680 (LWP 3598)]
[New Thread -1248400480 (LWP 3702)]
[KCrash handler]
#6  0xb726b544 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0xb726c311 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0xb7925e23 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#9  0xb725fe64 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb721a874 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0xb7282368 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0xb72821fe in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0xb726b0ff in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x0804fbca in main ()
Comment 8 Dario Andres 2009-10-02 03:19:51 UTC
Mh, if the last one is a complete backtrace it should be a Qt bug. 
If another crash is happening on the KDE4 version, please open a new bug report. Regards