[Kolab-devel] Crash in kde-runtime's kolabproxy (BT included)
Allen Winter
winter at kde.org
Sun Jul 29 18:33:15 CEST 2012
Howdy,
Attached is a backtrace I'm getting from the akonadi kolabproxy resource from kdepim-runtime.
I think this is a bug that should be handled in libkolab, but I'm not 100% sure about that.
Hoping that Christian can take a look.
I'm using libkolabxml v0.7.0 and libkolab 0.2.2 if that matters.
Regards,
Allen
-------------- next part --------------
warning: core file may not match specified executable file.
[New LWP 5877]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/data/kde/bin/akonadi_kolabproxy_resource --identifier akonadi_kolabproxy_resou'.
Program terminated with signal 11, Segmentation fault.
#0 0x00007f3a4cd74d72 in KCalCore::IncidenceBase::organizer (this=0x0) at /data/kde/trunk/KDE/kdepimlibs/kcalcore/incidencebase.cpp:277
277 return d->mOrganizer;
#0 0x00007f3a4cd74d72 in KCalCore::IncidenceBase::organizer (this=0x0) at /data/kde/trunk/KDE/kdepimlibs/kcalcore/incidencebase.cpp:277
#1 0x00007f3a4bdb49b7 in Kolab::Mime::createMessage (incidencePtr=..., mimetype=..., xKolabType=..., xml=..., v3=false, productId=...) at /usr/local/src/libkolab-0.2.2/mime/mimeutils.cpp:103
#2 0x00007f3a4bdaa240 in Kolab::KolabObjectWriter::writeTodo (i=..., v=<optimized out>, productId=..., tz=...) at /usr/local/src/libkolab-0.2.2/kolabformat/kolabobject.cpp:331
#3 0x0000000000436d03 in ?? ()
#4 0x00007fffb0eb2840 in ?? ()
#5 0x00007fffb0eb2920 in ?? ()
#6 0x00000000009ed7f0 in ?? ()
#7 0x00007fffb0eb28c0 in ?? ()
#8 0x0000000000a1a850 in ?? ()
#9 0x0000000000432f0c in ?? ()
#10 0x00000000007eb650 in ?? ()
#11 0x00007fffb0eb2920 in ?? ()
#12 0x0000000000000000 in ?? ()
More information about the devel
mailing list