Selective Mudflap

[Frank Ch. Eigler]

Hi -

On Fri, Sep 02, 2005 at 03:55:27PM +0100, Jon Levell wrote:
> [...]
> > Do these errors arise from malloc-type operations performed by the
> > JVM?  Or from your code's use of JVM-provided pointers?  [...]
> 
> 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"). [...]

"register" operations occur when a new memory-resident object is made
known to libmudflap.  If it overlaps with another existing object, a
"register" type error is indicated.  Chances are that it is ordinary
memory allocation performed by the JVM that is triggering the problem.

Unfortunately, from what I recall, the JVM invocation interface does
not include hooks to override the JVM's memory allocation primitives.
That, coupled with libmudflap's weaknesses with multithreaded
programs, makes this a difficult nut to crack.

- FChE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20050902/2bf7aa96/attachment.sig>