JRE exceptions

Question

Hi..
I have recently posted following message to the Java Runtime Environment (JRE) list. Unfrotunately i got no aswers. Maybe someone here can help me.
thanks!
Konrad Zagorowicz
Hi.
I am working on a win32 project that use java (via jre) as an extension to the c++ code. There are specific events in the c++ code that calls methods from java classes (via JNIEnv::CallVoidMethod and similar). Additionally java classes may have native methods defined. And here a problem shows up. When a native code has a bug that causes an exception (eg. access violation) the application closes immediately: no dialogbox and worse no debug stop. The only information about the bug and its location is the hs_err_pid*.log file. When a similar bug happens in none native code normal exception handling occurs. By normal I mean the debuger stops at a location where bug occured (usualy acces violation) or an appropriate messagebox is displayed. I tried to setup my own exception handlers by using win32 api calls:
setse_translator
setse_translator_function
SetUnhandledExceptionFilter
but it didnt work. JRE still handles exceptions in the native code. So here is my question: Can I some how turn off JRE excepition handling in the native code. Or maybe I can some how provide a callback to get informed about the exception. I tried to look for a solution in the jdk and in the archives but I found nothing.
thanks in advance
Konrad

Answer 1

Hi,
Recently I've had the same problem as yours and it took me a while to debug properly the issue. In the end, it was all documented in the setse_translator documentation page:
+" To specify a custom translation function, call _set_se_translator with the name of your translation function as its argument. The translator function that you write is called once for each function invocation on the stack that has try blocks. There is no default translator function.+
+Your translator function should do no more than throw a C++ typed exception. If it does anything in addition to throwing (such as writing to a log file, for example) your program might not behave as expected, because the number of times the translator function is invoked is platform-dependent. "+
JVM only creates the dumps and terminates when you end up with an unhandled exception. To prevent that you can use the __try/__except blocks (as the first answer suggested) or you can try the C++ approach:
void Java_...._myfunc(JNIEnv *e, jobject mythis) {
  try {
    _set_se_translator(my_se_translator_func);
   // do whatever you need
  } catch(const MySEMappedException & e) {
  }Regards,
Paulo.
Edited by: Paulo_P on Jun 6, 2009 8:37 PM