Re: [PATCH] exported-object: set object path after skeleton creation

On Thu, 2016-02-11 at 11:58 +0100, Beniamino Galvani wrote:
When exporting an object, we first set the object path and then
GDBus interface skeletons. While doing this, a signal can be
[1] and then nm_exported_object_signal_hook() can trigger the failed
assertion "interface != NULL" because the object is already exported
(priv->path != NULL) but the interface has not been registered yet.

To fix this, set the object path only after skeletons have been

looks good to me.



Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]