On 2012-09-07 15:29, Michael Meeks wrote:
On Fri, 2012-09-07 at 13:30 +0100, Caolán McNamara wrote:
FWIW, I patched the *internal* to be valgrind friendly when G_SLICE is
set. So if you have to debug something where python is alive you could
try building against the internal python and it should "just work" with
your usual export VALGRIND=memcheck foo
        Oooh ! that's insanely cool :-)
        Was just digging through a load of false-positives there myself.
        Now if only we could do something similar for Java :-)
Does valgrind's --smc-check=all not help?
Otherwise you could turn off the VM's JIT, there is a way of doing it 
from JNI. Search this page:
http://docs.oracle.com/javase/1.4.2/docs/guide/jni/jni-12.html 
<http://docs.oracle.com/javase/1.4.2/docs/guide/jni/jni-12.html>
for "JIT".
Regards, Noel Grandin
Disclaimer: http://www.peralex.com/disclaimer.html
Context
   
 
  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.