GLib-GIO-CRITICAL **: g_dbus_proxy_call_finish_internal: assertion 'error == NULL || *error == NULL' failed
Ali
aliovx at gmail.com
Tue May 9 15:08:52 CEST 2017
Hi Francesco,
This effectively can happen, the call might fail and it does not set a
reason for the failure. I assume you are initializing your error
pointer, you can like the following
...
GError *error = NULL;
result = g_dbus_proxy_call_finish(proxy, res, &error); if (error != NULL) {
g_warning("... %s", error->message);
g_error_free(error);
return;
}
if (result == NULL) {
g_warning("Failed with no specific error");
return;
}
Cheers,
Ali
On 04/29/2017 05:26 PM, Francesco Pasa wrote:
> Hi All,
>
> I am debugging the GTK3 port of Thunar. We have a rather serious bug
> affecting almost all file operations (copy, rename, move, etc), which
> results in a crash (segfault) of the program. I debugged a little and
> it seems that the error is coming from the funtion
>
> GVariant <https://developer.gnome.org/gio/glib-GVariant.html#GVariant> *
> g_dbus_proxy_call_finish (/|GDBusProxy <https://developer.gnome.org/gio/stable/GDBusProxy.html>
> *proxy|/,
> /|GAsyncResult
> <https://developer.gnome.org/gio/stable/GAsyncResult.html> *res|/,
> /|GError
> <https://developer.gnome.org/gio/glib-Error-Reporting.html#GError>
> **error|/);
> which is supposed to return NULL in case of errors, and fill the error
> pointer with a description of the error. It does return NULL, but the
> error pointer seems to be uninitialized (the bug goes away if I
> manually fill the error pointer with some random data and g_error_new).
>
> Does somebody now if this is a bug in glib?
>
> Thanks in advance,
> Francesco Pasa
>
>
>
>
> _______________________________________________
> Xfce4-dev mailing list
> Xfce4-dev at xfce.org
> https://mail.xfce.org/mailman/listinfo/xfce4-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.xfce.org/pipermail/xfce4-dev/attachments/20170509/b8d02101/attachment.html>
More information about the Xfce4-dev
mailing list