It'd be easier to see the C header and Java invocation to see whether
you've got your arguments set up properly. It doesn't take anything
more than a misplaced NULL pointer to kill the VM.
Almost all crashes are caused by invalid arguments.
I'm considering putting something in (optional) to catch and re-throw
these (since windows throws an access violation as a C++ exception)
but I haven't been able to get gcc to build with that behavior (don't
know if it's possible).
On Jul 12, 2007, at 12:13 PM, <bb...@cox.net> <bb...@cox.net> wrote:
My JNA project is coming along, slowly, but I have hit a brick
wall. Before delving further, what are the possible causes of:
# An unexpected error has been detected by Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x003ef975,
pid=828, tid=832
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0_01-b06 mixed mode)
# Problematic frame:
# C 0x003ef975
#
# An error report file with more information is saved as
hs_err_pid828.log
I've seen earlier people hitting this when picking the wrong one
of: StdCallLibary, Library
For giggles, I changed mine to the other... no, that's definitely
not causing my problem.
In the debugger, this crash occurs when I "Step Into" invokeInt().
(Uh, is there some way to step into a native method? I'm using
Eclipse...)
So, either it's a crash setting up the arguments, within the .dll
function I'm calling, or cleaning up after the call. (Can all of
these cause a crash like the above, or do crashes within the .dll
look different?)
2 messages in net.java.dev.jna.usersRe: [jna-users] causes for JRE EXCEPT...
