Re: valgrinding with python stuff active

Stephan Bergmann <sbergman -AT- redhat.com>
Mon, 10 Sep 2012 12:28:33 +0200

On 09/09/2012 12:45 AM, 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

Fixed now as<https://wiki.documentfoundation.org/index.php?title=BugReport&oldid=55245#How_to_get_valgrind_log_.28on_Linux.29>;the real fix is to valgrind soffice rather than soffice.bin (as theformer shell script already takes care of setting G_SLICE=always-mallocetc. when run under valgrind memcheck).


Stephan

Context

Re: valgrinding with python stuff active (continued)
- Re: valgrinding with python stuff active · Michael Meeks
  - valgrinding with java stuff active · Noel Grandin
  - Re: valgrinding with python stuff active · Stephan Bergmann
    - Re: valgrinding with python stuff active · Michael Meeks
      - Re: valgrinding with python stuff active · julien2412
        
        Re: valgrinding with python stuff active / no more false positives with valgrind 3.7? · Andrzej J. R. Hunt
        
        Re: valgrinding with python stuff active / no more false positives with valgrind 3.7? · Julien Nabet
        
        Re: valgrinding with python stuff active · Norbert Thiebaud
        
        Re: valgrinding with python stuff active · Julien Nabet
        
        Re: valgrinding with python stuff active · Michael Meeks
        
        Re: valgrinding with python stuff active · Stephan Bergmann

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.