[Interest] ideas how to debug this crash?
René J.V. Bertin
rjvbertin at gmail.com
Tue Dec 8 00:12:27 CET 2015
Hi,
Here's a backtrace I'm seeing under certain conditions in an application (a KF5 application built on/for OS X, kdebugdialog5):
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 org.qt-project.QtDBus 0x000000010d33d9b6 QHashNode<QString, QDBusConnectionPrivate::SignalHook>::~QHashNode() + 166 (qgenericatomic.h:90)
1 org.qt-project.QtCore 0x000000010e38d9b9 QHashData::free_helper(void (*)(QHashData::Node*)) + 73 (qhash.cpp:405)
2 org.qt-project.QtDBus 0x000000010d3311a8 QDBusConnectionPrivate::~QDBusConnectionPrivate() + 712 (qhash.h:342)
3 org.qt-project.QtDBus 0x000000010d3315ce QDBusConnectionPrivate::~QDBusConnectionPrivate() + 14 (qdbusintegrator.cpp:1035)
4 org.qt-project.QtDBus 0x000000010d329af8 (anonymous namespace)::Q_QGS__q_sessionBus::innerFunction()::Cleanup::~Cleanup() + 152 (qdbusconnection.cpp:1079)
5 libsystem_c.dylib 0x00007fff89e5d7a1 __cxa_finalize + 177
6 libsystem_c.dylib 0x00007fff89e5da4c exit + 22
7 libdyld.dylib 0x00007fff8e8b0604 start + 8
Any ideas how to figure out the culprit?
NB: this involves a QPlatformPlugin which accesses the DBus, but a priori the same accesses are made in applications that never crash.
If possible I'd like to avoid using valgrind, because that's been a great tool mostly to cause KPs :-/
Thanks!
R.
More information about the Interest
mailing list