Web lists-archives.com

Re: SIGTRAP when sending signal on closing dbus connection




Hi Jean-Pierre,

you should not be using the same object from different threads, instead you should probably idle to the main thread and to the signal from there.

Cheers.

Adding you to the gtk mailing list btw.

On Tue, Jun 16, 2015 at 12:14 PM, <Jean-Pierre.Bogler@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:


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
_______________________________________________
gnome-devel-list mailing list
gnome-devel-list@xxxxxxxxx
https://mail.gnome.org/mailman/listinfo/gnome-devel-list




--
Ignacio Casal Quinteiro
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@xxxxxxxxx
https://mail.gnome.org/mailman/listinfo/gtk-devel-list