Ah, that explains it. Yes, the debugger will always trap the access
violation before the VM gets a chance to handle it. The way the VM
handles null dereferences is to install an OS-level handler using
AddVectoredExceptionHandler so it can turn the access violation into a
Java-level exception. The debugger steps in before the VM's handler
gets a chance, and unless the debugger gives you a way resume
execution and allow the VM's handler to run (GDB lets you do that, I
don't know about Windows debuggers), the program will crash.
Glad you figured it out.
> --
> You received this message because you are subscribed to the Google Groups
> "Avian" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
avian+un...@googlegroups.com.
> To post to this group, send email to
av...@googlegroups.com.
> Visit this group at
https://groups.google.com/group/avian.
> For more options, visit
https://groups.google.com/d/optout.