Array-Size

[Havoc Pennington]

> 
> ==7950== Syscall param writev(vector[...]) points to uninitialised byte(s)
> ==7950==    at 0x4203986: do_writev (in /lib/tls/libc-2.3.5.so)
> ==7950==    by 0x80627A9: _dbus_write_two (dbus-sysdeps.c:338)

This may well be bogus (no reason to init parts of the buffer that don't 
have data in them, but valgrind warns anyway)

> ==7961== LEAK SUMMARY:
> ==7961==    definitely lost: 302 bytes in 16 blocks.
> ==7961==      possibly lost: 130 bytes in 4 blocks.
> ==7961==    still reachable: 100,671,104 bytes in 59 blocks.
> ==7961==         suppressed: 0 bytes in 0 blocks.
> 
> Still reachable is about 100MB?!? Does dbus internally copy
> the array twice?

dbus will copy it into the DBusMessage. That should be all though.

Most of the bindings create an extra copy into their native data type, 
though.

If you track it down to a bug, let us know... or provide a simple, 
compilable test case so someone can have a look.

Havoc