Re: valgrinding with python stuff active

On Sun, 2012-09-09 at 00:45 +0200, Julien Nabet wrote:
> So in 
> http://wiki.documentfoundation.org/BugReport#How_to_get_valgrind_log_.28on_Linux.29 
> page, should I add this:
>
> export G_SLICE=always-malloc
>
> before this:
>
> valgrind --tool=memcheck --num-callers=50 --trace-children=yes ./soffice.bin 2>&1 | tee 
> /tmp/valgrind.log

        Yes :-) that's critical.

        Having said that - since we now have a nice configure check for /
include valgrind.h already in:

jvmfwk/plugins/sunmajor/pluginlib/sunjavaplugin.cxx:#include <valgrind.h>

        I suspect we should (perhaps) do just the same thing in our code to
drop our custom allocator, and for good measure check before g_type_init
- and do a putenv("G_SLICE=1"); to clobber glib.

        Then we can remove that from the docs again I suppose :-) patches
welcome for that.

        ATB,

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot