How to debug dbus errors for app development?

asked 2019-05-12 19:19:16 +0300

jsommer
3324 ●97 ●142 ●154

I use the approach of the harbour-batteryoverlay and harbour-screentapshot for an overly feature.

If I close the app or deactivate the overlay, I can see a dbus error in the log and the app crashes:

process 26992: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1367.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace

The view helper class executes the following code:

if (overlayView) {
    QDBusConnection::sessionBus().unregisterObject("MyApp/overlay");
    QDBusConnection::sessionBus().unregisterService("MyApp.overlay");
    overlayView->close();
    delete overlayView;
    overlayView = NULL;
}
else {
    QDBusInterface iface("MyApp.overlay", "MyApp/overlay", "MyApp");
    iface.call(QDBus::NoBlock, "exit");
}

Some ideas?