Finding memory corruption in a mixed Java/C(++) application (#926180 scilab)

["Rebecca N. Palmer" <rebecca_palmer@zoho.com>]

Scilab is an application containing Java, C and C++ code, which 
sometimes crashes with what looks like memory corruption.  As this bug 
can happen during build (building the documentation involves running the 
application), it is considered RC [0].

I attempted to locate this bug using Valgrind, but found that it reports 
a huge number of "errors" in even small Java applications such as jar, 
suggesting that it can't properly track memory allocated/used by Java. 
The Valgrind documentation [1] says --smc-check=all should fix this, but 
it does not.

Any suggestions for better ways to find this bug?

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926180
[1] http://www.valgrind.org/docs/manual/faq.html#faq.java