LWJGL seems to set up a native exception handler

Started by fred_em, December 13, 2010, 14:22:57

Previous topic - Next topic

fred_em

Hi,

LWJGL seems to set up a native exception handler, at least on Win32.

My application is written in Java mostly, with some parts written in C++. Either from the Java or C++ side of the code, I need to make use of OpenGL.

Since I have been using LWJGL I have a big problem under Visual C++ 2008, whereby the debugger no longer stops when a system exception occurs, like an access violation. I do need to debug crashes occuring in C++. The VS 2008 debugger is great for this, as it automatically attaches to the Java process, find the offending module (a DLL in my case) and shows you the source and the offending line of code.

Well, with LWJGL all of this doesn't work anymore.

This could be because LWJGL tries to swallow exceptions with a global exception handler, (AddVectoredExceptionHandler, see MSDN).

How can I prevent LWJGL to setup such an exception handler?

Fred

fred_em

Please disregard the previous post.

I do have something very strange going on when I'm in a debug session, but it seems unrelated to LWJGL.