search for: g_slice

...ed leaks in the libosinfo code (in which case we > should suppress them), I think this might have to do with the glib allocator (libosinfo is based on glib, so it allocate using it), that allocates in chunks by default to avoid fragmentation, IIRC. Do you still get the same issues if you export G_SLICE=always-malloc when running valgrind? > or if they are actual bugs because we are > missing a true destructor here: > > https://github.com/libguestfs/virt-v2v/blob/8e870da79b5a61513f568b0b81c773084b8d7997/v2v/libosinfo-c.c#L91 > > Perhaps there's a reason why we cannot hav...

Hi Pino: I've suppressed some OCaml and libosinfo valgrind errors in virt-v2v. The remaining valgrind errors are here: http://oirase.annexia.org/tmp/v2vvg/ They all seem to be basically the same. But I couldn't work out if these are expected leaks in the libosinfo code (in which case we should suppress them), or if they are actual bugs because we are missing a true destructor here:

...f [ -z "$GI_TYPELIB_PATH" ]; then - GI_TYPELIB_PATH="$b/gobject" -else - GI_TYPELIB_PATH="$b/gobject:$GI_TYPELIB_PATH" -fi +prepend GI_TYPELIB_PATH "$b/gobject" export GI_TYPELIB_PATH # Be friendly to valgrind (https://live.gnome.org/Valgrind) export G_SLICE=always-malloc -- 2.1.0