Memory leak in gdbus-codegen generated code

I have an interface described in DBus Introspection XML format:

    <!DOCTYPE node PUBLIC "-//freedesktop//DTD D-BUS Object Introspection 1.0//EN"
      <interface name="">
        <method name="Bar" />

I run gdbus-codegen like this:

    gdbus-codegen --interface-prefix=com.example --generate-c-code=foo-dbus --c-namespace=Dbus foo.xml

I use the code like this:

    int main()
        DbusFoo * skeleton = dbus_foo_skeleton_new();

        return 0;

But the application ends up leaking the signal generated in `dbus_foo_default_init()` which looks like this:

    static void
    dbus_foo_default_init (DbusFooIface *iface)
      /* GObject signals for incoming D-Bus method calls: */
       * DbusFoo::handle-bar:
       * @object: A #DbusFoo.
       * @invocation: A #GDBusMethodInvocation.
       * Signal emitted when a remote caller is invoking the <link 
linkend="gdbus-method-com-example-foo.Bar">Bar()</link> D-Bus method.
       * If a signal handler returns %TRUE, it means the signal handler will handle the invocation (e.g. take 
a reference to @invocation and eventually call dbus_foo_complete_bar() or e.g. 
g_dbus_method_invocation_return_error() on it) and no order signal handlers will run. If no signal handler 
handles the invocation, the %G_DBUS_ERROR_UNKNOWN_METHOD error is returned.
       * Returns: %TRUE if the invocation was handled, %FALSE to let other signal handlers run.
      g_signal_new ("handle-bar",
        G_TYPE_FROM_INTERFACE (iface),
        G_STRUCT_OFFSET (DbusFooIface, handle_bar),


Am I using the generated code wrong or is it a bug in glib/gdbus-codegen?

This message is subject to the following terms and conditions: MAIL 

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