I have a problem with Dbus-Glib

Colin Walters walters at verbum.org
Mon Feb 2 14:30:32 PST 2009

On Sat, Jan 31, 2009 at 3:04 PM, MeduZa <meduzapat at netscape.net> wrote:
> can some one explain me how dbus_g_proxy_call works (I already read the
> documentation but I don't understand with dbus_g_proxy_call eat memory
> every time I use it)

Most likely you're passing an allocated argument and not freeing it
afterwards.  For example, your code is g_strdup()ing a string, but
neglecting to free it after the call.

Your best bet is a tool like valgrind (http://valgrind.org/).

More information about the dbus mailing list