SIGTRAP when sending signal on closing dbus connection

Dies ist eine mehrteilige Nachricht im MIME-Format.
--===============9221431473770579862==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline



--===============9221431473770579862==
Content-Type: multipart/alternative; boundary="=_alternative 00384A1BC1257E66_="

Dies ist eine mehrteilige Nachricht im MIME-Format.
--=_alternative 00384A1BC1257E66_=
Content-Type: text/plain; charset="US-ASCII"

Hi *,

in a multi threaded application we are receiving a SIGTRAP, while using 
gdbus. 
In short terms, the application is doing the following:

Thread 1: g_object_unref(connection);
Thread 2: g_dbus_connection_emit_signal(connection);

The SIGTRAP is raised when a "pthread_mutex_trylock" fails, in the 
callstack of 
"g_dbus_connection_emit_signal", because the mutex already is invalid. I 
assumed 
that gdbus is thread safe at this point. Is this assumption wrong or is 
there really 
a bug?

In case more details are requried, please let me know. I can easily 
reproduce the 
issue at my place and already implemented a small test executable.

Best regards
Jean-Pierre
--=_alternative 00384A1BC1257E66_=
Content-Type: text/html; charset="US-ASCII"

<tt><font size=2>Hi *,</font></tt>
<br>
<br><tt><font size=2>in a multi threaded application we are receiving a
SIGTRAP, while using gdbus. </font></tt>
<br><tt><font size=2>In short terms, the application is doing the following:</font></tt>
<br>
<br><tt><font size=2>Thread 1: g_object_unref(connection);</font></tt>
<br><tt><font size=2>Thread 2: g_dbus_connection_emit_signal(connection);</font></tt>
<br>
<br><tt><font size=2>The SIGTRAP is raised when a &quot;pthread_mutex_trylock&quot;
fails, in the callstack of </font></tt>
<br><tt><font size=2>&quot;g_dbus_connection_emit_signal&quot;, because
the mutex already is invalid. I assumed </font></tt>
<br><tt><font size=2>that gdbus is thread safe at this point. Is this assumption
wrong or is there really </font></tt>
<br><tt><font size=2>a bug?</font></tt>
<br>
<br><tt><font size=2>In case more details are requried, please let me know.
I can easily reproduce the </font></tt>
<br><tt><font size=2>issue at my place and already implemented a small
test executable.</font></tt>
<br>
<br><tt><font size=2>Best regards</font></tt>
<br><tt><font size=2>Jean-Pierre</font></tt>
--=_alternative 00384A1BC1257E66_=--

--===============9221431473770579862==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
gnome-devel-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/gnome-devel-list

--===============9221431473770579862==--