Causing the JNI code to crash "properly"
I have some code written in C and liked to Java using JNI.
When I run it (even from the Visual C++ environment) and the code gets an exception in C, the JVM catches it and closes up nicely with an error.
What can I do to remove this behavior and let it crash - this will cause Visual C++ debugger to catch it and show me where the crash is.
I've got 2 problems with this:
1. I'm writiing code in pure ANSI C - so try/catch doesn't work for me in the long run - just as a way of debugging a specific problem.
2. I need something that will crash - not something that will get over it, but something that will be able to show me the exact problem, along with a backtrace, values of variables, and the ability to use a debugger to check the memory while I'm at it.
I will try it though, so thanks a lot
- 1Billing doc splitting to different cocodes 10-11
- 2Error message while transporting SapScript to productive system 10-11
- 3ENVY14, started getting, "this copy of windows is not genuine" message. Spoke with HP tech, 10-11
- 4All PDF's show up as bad files 10-11
- 5How to create a database in 11g from an archive taken from 10g 10-11
- 6Stretching Table with IE8 compatibility view 10-11
- 7For Forum Admin: Problem with this forum editor 10-11
- 8Black border around dialog box, buttons, and everywhere 10-11
- Incorrect condition evaluation for content-based routing (Receiver determ.)10/11
- IMac Black Screen with fans running...Static damage?10/11
- When I updated to 7.0.6 my calendar events were lost11/30
- Printing in tray1 - Smartforms11/30
- How to render faster when working on project11/30
- Adobe AIR + Flex Application11/30
- I'm using OS X 10.6.8 my airport utility isnt working11/30
- Committed Date For Components in Production Order11/30
- Possible to have a 23.97 fps scene in 29.97 fps project?11/30
- 5.2 CC SP9 Rule Export Problem11/30