Memory leak in dbus / dbus-c++ ?

[Thiago Macieira]

Olivier Hochreutiner wrote:
>I used BoundChecker to detect where the memory that is not freed in
>allocated. It reports three places in the code (see attached file). I
>investigated the problem a bit and it seems that reply messages are
>not freed ?

DBusMessage memory blocks are recycled for reuse internally. That 
shouldn't count as memory leaks, because there are still pointers to the 
blocks.

However, they would be memory leaks if the binding doesn't properly call 
dbus_message_unref.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freedesktop.org/archives/dbus/attachments/20070731/064ad0ce/attachment.pgp