Application that crashed: choqok Version of the application: 1.0 Alpha2 (0.9.4) KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.32-trunk-amd64 x86_64 Distribution: Debian GNU/Linux unstable (sid) What I was doing when the application crashed: Choqok segfaulted after doing a Quick Post to an identi.ca and twitter account. The post was delivered successfully. -- Backtrace: Application: Choqok (choqok), signal: Segmentation fault [KCrash Handler] #6 QBasicAtomicInt::deref (this=0xa5a4900, other=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:132 #7 QString::operator= (this=0xa5a4900, other=...) at tools/qstring.cpp:1132 #8 0xf3c15b53 in TwitterApiMicroBlog::readPostFromDomElement(Choqok::Account*, QDomElement const&, Choqok::Post*) () from /usr/lib/libtwitterapihelper.so.0 #9 0xf3c09609 in TwitterApiMicroBlog::readPostFromXml(Choqok::Account*, QByteArray const&, Choqok::Post*) () from /usr/lib/libtwitterapihelper.so.0 #10 0xf3c1b4af in TwitterApiMicroBlog::slotCreatePost(KJob*) () from /usr/lib/libtwitterapihelper.so.0 #11 0xf3c113e2 in TwitterApiMicroBlog::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libtwitterapihelper.so.0 #12 0xf3c57c62 in ?? () from /usr/lib/kde4/choqok_laconica.so #13 0xf6ce7303 in QMetaObject::activate (sender=0xaa2f738, from_signal_index=7, to_signal_index=7, argv=0xff8b987c) at kernel/qobject.cpp:3112 #14 0xf6ce7f42 in QMetaObject::activate (sender=0xaa2f738, m=0xf7075888, local_signal_index=3, argv=0xff8b987c) at kernel/qobject.cpp:3186 #15 0xf6f12a33 in KJob::result (this=0xaa2f738, _t1=0xaa2f738) at ./kjob.moc:188 #16 0xf6f12ed9 in KJob::emitResult (this=0xaa2f738) at ../../kdecore/jobs/kjob.cpp:304 #17 0xf71e6b15 in KIO::SimpleJob::slotFinished (this=0xaa2f738) at ../../kio/kio/job.cpp:477 #18 0xf71e7473 in KIO::TransferJob::slotFinished (this=0xaa2f738) at ../../kio/kio/job.cpp:948 #19 0xf71e3a03 in KIO::TransferJob::qt_metacall (this=0xaa2f738, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xff8b9ae8) at ./jobclasses.moc:343 #20 0xf71e3d2a in KIO::StoredTransferJob::qt_metacall (this=0xaa2f738, _c=QMetaObject::InvokeMetaMethod, _id=47, _a=0xff8b9ae8) at ./jobclasses.moc:447 #21 0xf6ce7303 in QMetaObject::activate (sender=0xa76a650, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3112 #22 0xf6ce7f42 in QMetaObject::activate (sender=0xa76a650, m=0xf738db84, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3186 #23 0xf72ac707 in KIO::SlaveInterface::finished (this=0xa76a650) at ./slaveinterface.moc:165 #24 0xf72b04b7 in KIO::SlaveInterface::dispatch (this=0xa76a650, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175 #25 0xf72acbe7 in KIO::SlaveInterface::dispatch (this=0xa76a650) at ../../kio/kio/slaveinterface.cpp:91 #26 0xf729ebcd in KIO::Slave::gotInput (this=0xa76a650) at ../../kio/kio/slave.cpp:322 #27 0xf72a10b3 in KIO::Slave::qt_metacall (this=0xa76a650, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xff8b9db8) at ./slave.moc:76 #28 0xf6ce7303 in QMetaObject::activate (sender=0xa3bd3a0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #29 0xf6ce7f42 in QMetaObject::activate (sender=0xa3bd3a0, m=0xf738a4c0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #30 0xf71aac07 in KIO::Connection::readyRead (this=0xa3bd3a0) at ./connection.moc:86 #31 0xf71ac513 in KIO::ConnectionPrivate::dequeue (this=0xaa4d118) at ../../kio/kio/connection.cpp:82 #32 0xf71ac8f6 in KIO::Connection::qt_metacall (this=0xa3bd3a0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xa3f0170) at ./connection.moc:73 #33 0xf6ce0b0b in QMetaCallEvent::placeMetaCall (this=0xaa4a830, object=0xa3bd3a0) at kernel/qobject.cpp:477 #34 0xf6ce25e0 in QObject::event (this=0xa3bd3a0, e=0xaa4a830) at kernel/qobject.cpp:1110 #35 0xf61b4a94 in QApplicationPrivate::notify_helper (this=0xa031a70, receiver=0xa3bd3a0, e=0xaa4a830) at kernel/qapplication.cpp:4065 #36 0xf61bcbee in QApplication::notify (this=0xff8ba5cc, receiver=0xa3bd3a0, e=0xaa4a830) at kernel/qapplication.cpp:3605 #37 0xf75b062d in KApplication::notify (this=0xff8ba5cc, receiver=0xa3bd3a0, event=0xaa4a830) at ../../kdeui/kernel/kapplication.cpp:302 #38 0xf6cd21eb in QCoreApplication::notifyInternal (this=0xff8ba5cc, receiver=0xa3bd3a0, event=0xaa4a830) at kernel/qcoreapplication.cpp:610 #39 0xf6cd2e2e in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0xa01afe0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #40 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xa01afe0) at kernel/qcoreapplication.cpp:1247 #41 0xf6cd300d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #42 0xf6cfd4cf in QCoreApplication::sendPostedEvents (s=0xa0346a0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #43 postEventSourceDispatch (s=0xa0346a0) at kernel/qeventdispatcher_glib.cpp:276 #44 0xf5a9bb38 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #45 0xf5a9f3d0 in ?? () from /lib/libglib-2.0.so.0 #46 0xf5a9f503 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #47 0xf6cfd041 in QEventDispatcherGlib::processEvents (this=0xa0319a8, flags=...) at kernel/qeventdispatcher_glib.cpp:407 #48 0xf6254305 in QGuiEventDispatcherGlib::processEvents (this=0xa0319a8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #49 0xf6cd083a in QEventLoop::processEvents (this=0xff8ba540, flags=...) at kernel/qeventloop.cpp:149 #50 0xf6cd0c82 in QEventLoop::exec (this=0xff8ba540, flags=...) at kernel/qeventloop.cpp:201 #51 0xf6cd30d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #52 0xf61b4917 in QApplication::exec () at kernel/qapplication.cpp:3525 #53 0x0805563b in _start () Reported using DrKonqi
Also worth noting, this occurred in a build based on the most recent git snapshot from gitorious.org as of 2009-12-30
And, of course, it worked fine on a second try, with no crash. If nobody else can reproduce this problem, it might not be worth spending too much time on.
This is being tracked at bug 209203. Thanks *** This bug has been marked as a duplicate of bug 209203 ***