I just noticed this in JNA...could be new?
setProtected
public static void setProtected(boolean enable)
Set whether native memory accesses are protected from invalid
accesses. This should only be set true when testing or debugging, and
should not be considered reliable or robust for multi
I have not noticed it before. I wonder why it is not recommended for
anything but testing/debugging? Perhaps it slows things down in some
way?
-Tom
On Jan 19, 2008 4:27 AM, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote:
> I just noticed this in JNA...could be new?
>
> setProtected
>
> public
Slowdown is one reason, interfering with code is another.
On unixen, it installs/uninstalls a SIGSEGV and a SIGBUS handler every
time you invoke a native function or do memory copies, basically
anything that might touch native memory.
Some native code (possibly the jvm itself) uses SIGSEGV for it
