[Kolab-devel] [issue314] segfault in kontact
Bernhard Herzog
kolab-issues at intevation.de
Tue Aug 17 19:30:31 CEST 2004
New submission from Bernhard Herzog <bh at intevation.de>:
I just got a sefault in kontact while I was editing an event (kdepim proko2_m3
tag). I can't reliably reproduce it, though.
[New Thread 1024 (LWP 23084)]
0x4176da59 in wait4 () from /lib/libc.so.6
#0 0x4176da59 in wait4 () from /lib/libc.so.6
#1 0x417e4e48 in __check_rhosts_file () from /lib/libc.so.6
#2 0x41653453 in waitpid () from /lib/libpthread.so.0
#3 0x40b2c5dd in KCrash::defaultCrashHandler (sig=11) at kcrash.cpp:246
#4 0x41650f54 in pthread_sighandler () from /lib/libpthread.so.0
#5 0x416f66b8 in sigaction () from /lib/libc.so.6
#6 0x42080efe in KMailICalIfaceImpl::subresourcesKolab (this=0x818a528,
contentsType=@0xbfffeec8) at kmailicalifaceimpl.cpp:656
#7 0x420d6475 in KMailICalIface::process (this=0x818a5a8, fun=@0xbffff048,
data=@0xbffff050, replyType=@0xbffff058, replyData=@0xbffff02c)
at kmailicalIface_skel.cpp:194
#8 0x40c1b33e in DCOPClient::receive (this=0x813a260, objId=@0xbffff040,
fun=@0xbffff048, data=@0xbffff050, replyType=@0xbffff058,
replyData=@0xbffff02c) at dcopclient.cpp:1602
#9 0x40c157e4 in DCOPProcessInternal (d=0x813e918, opcode=2, key=68,
dataReceived=@0xbffff104, canPost=true) at dcopclient.cpp:508
#10 0x40c1518e in DCOPProcessMessage (iceConn=0x813a1d8,
clientObject=0x813e918, opcode=2, length=95, replyWait=0x0,
replyWaitRet=0xbffff174) at dcopclient.cpp:419
#11 0x40c29995 in KDE_IceProcessMessages (iceConn=0x813a1d8, replyWait=0x0,
replyReadyRet=0x0) at process.c:325
#12 0x40c1c846 in DCOPClient::processSocketData (this=0x813a260, fd=11)
at dcopclient.cpp:1945
#13 0x40c1dfb1 in DCOPClient::qt_invoke (this=0x813a260, _id=2, _o=0xbffff314)
at dcopclient.moc:174
#14 0x40f6e32a in QObject::activate_signal (this=0x813ec60, clist=0x813a168,
o=0xbffff314) at kernel/qobject.cpp:2333
#15 0x40f6e6f3 in QObject::activate_signal (this=0x813ec60, signal=2, param=11)
at kernel/qobject.cpp:2426
#16 0x412bf9da in QSocketNotifier::activated (this=0x813ec60, t0=11)
at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#17 0x40f8c8a2 in QSocketNotifier::event (this=0x813ec60, e=0xbffff588)
at kernel/qsocketnotifier.cpp:271
#18 0x40f07cd5 in QApplication::internalNotify (this=0xbffff7e8,
receiver=0x813ec60, e=0xbffff588) at kernel/qapplication.cpp:2582
#19 0x40f06dbb in QApplication::notify (this=0xbffff7e8, receiver=0x813ec60,
e=0xbffff588) at kernel/qapplication.cpp:2305
#20 0x40a9f5b9 in KApplication::notify (this=0xbffff7e8, receiver=0x813ec60,
event=0xbffff588) at kapplication.cpp:507
#21 0x412b5d94 in QApplication::sendEvent (receiver=0x813ec60,
event=0xbffff588) at .moc/debug-shared-mt/../../kernel/qapplication.h:492
#22 0x40ef66e2 in QEventLoop::activateSocketNotifiers (this=0x80b0ed8)
at kernel/qeventloop_unix.cpp:579
#23 0x40eb0a3c in QEventLoop::processEvents (this=0x80b0ed8, flags=4)
at kernel/qeventloop_x11.cpp:340
#24 0x40f1e290 in QEventLoop::enterLoop (this=0x80b0ed8)
at kernel/qeventloop.cpp:198
#25 0x40f1e1c9 in QEventLoop::exec (this=0x80b0ed8)
at kernel/qeventloop.cpp:145
#26 0x40f07e8d in QApplication::exec (this=0xbffff7e8)
at kernel/qapplication.cpp:2705
#27 0x0805b381 in main (argc=1, argv=0xbffff974) at main.cpp:153
----------
assignedto: bo
messages: 1368
nosy: bh, bo
priority: bug
status: unread
title: segfault in kontact
topic: kde client
________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://intevation.de/roundup/kolab/issue314>
________________________________________________
More information about the devel
mailing list