Re: Selective Mudflap

["Jon Levell" <jon at coralbark dot net>]

"Frank Ch. Eigler" <fche@redhat.com> writes:
> "Jon Levell" <jon@coralbark.net> writes:
> > I'm trying to debug a large C application that (amongst other 
> > things) starts a JVM and uses Java's JDBC to connect to 
> > databases via JNI.
[..]
> > of errors (none from the JVM). I'd also like to use Mudflap however
> > running the program with mudflap generates huge numbers of errors
> > caused by the (uninstrumented) libjvm.so. [...]
> 
> Do these errors arise from malloc-type operations performed by the
> JVM?  Or from your code's use of JVM-provided pointers?  Sadly, there

The errors stem from inside the JVM. I presume when it is using 
pointers that the C application has provided because it was't 
compiled with mudflap itself. (I'm new to mudflap but the violations
claim to be of type "register").

> is no valgrind-style exclusion facility around.  However, if the JVM
> interface is used predominantly in one direction (C code calling into
> the JVM), it may be possible to programatically turn off mudflap
> enforcement when your code is about to jump into the jvm.  Maybe

There is quite a lot of interaction so for now I'll use a script to
post-process the Mudflap report. Because Mudflap is OSS, if someone
else doesn't do it first, I might at some point add some simple way 
to exclude violations but that won't be any time soon - things are
hectic here at the moment.

Thank you very much for your prompt response and for Mudflap, it
seems to be a very clever piece of software.

Jon.