Bug 57153 - Crash while syncing ToDo list
Summary: Crash while syncing ToDo list
Status: RESOLVED NOT A BUG
Alias: None
Product: kpilot
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: groot
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-12 09:08 UTC by ralphdewitt
Modified: 2004-10-19 16:20 UTC (History)
0 users

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 ralphdewitt 2003-04-12 09:08:47 UTC
Version:            (using KDE 3.1.1)
Compiler:          gcc version 3.2.2
OS:          Linux (i686) release 2.4.20-gentoo-r2

Kpilot crashes while launching sync with to do list. This is the back trace:

(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)...[New Thread 16384 (LWP 17233)]
(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)...
0x411b15d9 in wait4 () from /lib/libc.so.6
#0  0x411b15d9 in wait4 () from /lib/libc.so.6
#1  0x4122c20c in __DTOR_END__ () from /lib/libc.so.6
#2  0x40f5b8c3 in waitpid () from /lib/libpthread.so.0
#3  0x4066d84e in KCrash::defaultCrashHandler(int) ()
   from /usr/kde/3.1/lib/libkdecore.so.4
#4  <signal handler called>
#5  0x41b59cf0 in KNotesAction::process() ()
   from /usr/kde/3.1/lib/kde3/libknotesconduit.so.0
#6  0x41b5895d in KNotesAction::qt_invoke(int, QUObject*) ()
   from /usr/kde/3.1/lib/kde3/libknotesconduit.so.0
#7  0x40a09639 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/qt/3/lib/libqt-mt.so.3
#8  0x40a094dd in QObject::activate_signal(int) ()
   from /usr/qt/3/lib/libqt-mt.so.3
#9  0x40ceca7b in QTimer::timeout() () from /usr/qt/3/lib/libqt-mt.so.3
#10 0x40a2a782 in QTimer::event(QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3
#11 0x409ab644 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/qt/3/lib/libqt-mt.so.3
#12 0x409aabbb in QApplication::notify(QObject*, QEvent*) ()
   from /usr/qt/3/lib/libqt-mt.so.3
#13 0x405e1529 in KApplication::notify(QObject*, QEvent*) ()
   from /usr/kde/3.1/lib/libkdecore.so.4
#14 0x409861d3 in QEventLoop::activateTimers() ()
   from /usr/qt/3/lib/libqt-mt.so.3
#15 0x409639a8 in QEventLoop::processEvents(unsigned) ()
   from /usr/qt/3/lib/libqt-mt.so.3
#16 0x409bf466 in QEventLoop::enterLoop() () from /usr/qt/3/lib/libqt-mt.so.3
#17 0x409bf308 in QEventLoop::exec() () from /usr/qt/3/lib/libqt-mt.so.3
#18 0x409ab871 in QApplication::exec() () from /usr/qt/3/lib/libqt-mt.so.3
#19 0x080563c2 in QFrame::paintEvent(QPaintEvent*) ()
#20 0x4111bdc4 in __libc_start_main () from /lib/libc.so.6
Comment 1 Reinhold Kainhofer 2003-07-30 01:28:50 UTC
The backtrace says that the crash appeared in Qt code while loading the knotes 
conduit. Thus this is not a problem in KPilot's code, but most probably a binary 
compatibility issue either with an updated Qt or a version mismatch between kpilot and 
the knotes conduit/