System.setProperty("jna.protected", "true")
or open the launch properties in eclipse and add "-
Djna.protected=true" to the vm args.
On Aug 20, 2008, at 11:12 AM, Stas Oskin wrote:
Thanks for the tip!
Do you know by chance how it's possible to set the system property
in Eclipse?
Or it should be set by some function in the code?
Thanks again.
2008/8/20, Timothy Wall <twal...@dev.java.net>:
If you set the system property "jna.protected=true", you should get
a thrown
Error instead of a VM crash.
That's only if the crash occurs within a JNA call; if the crash is
independent of JNA, you'll need to attach a debugger to the process.
On Aug 20, 2008, at 10:18 AM, Stas Oskin wrote:
Hi.
Every time my app crashes in the native code, I spent a lot of time
using debug printing to find the source of the crashes.
If I'd knew the calling Java function where the crash has
occurred, it
would be much simpler. Any idea how it's possible to print the full
Java stuck before the VM crash?
5 messages in net.java.dev.jna.usersRe: [jna-users] VM crash Java code stuck
