There is a very poor documentation of which exceptions are actually thrown from which JDI method.
We need to put try/catch block around every JDI call and catch the errors. It looks like the errors are better
documented in the description of JDWP protocol -
http://java.sun.com/javase/6/docs/platform/jpda/jdwp/jdwp-protocol.html. This can provide hints on which exceptions are
thrown from corresponding JDI methods.
Scheduling for 7.0.
The intended implementation of this is to generate wrappers for JDI methods and checked wrapper exceptions.
Every method should clearly specify what exception can be thrown from it and the code needs to catch these exceptions.
JDI methods should not be called directly, but only through the wrappers. This will prevent from unexpected exceptions.
Also, the wrappers can automatically catch pathological exceptions, like InternalErrors, which do occur, sometimes.
InternalExceptions can be handled more gracefully - see e.g. issue #54624.
Wrappers for JDI methods are generated, they throw checked exceptions that must be caught in the code. All class to JDI
are rewritten to use the wrapper methods in debugger.jpda module:
Integrated into 'main-golden', will be available in build *200812231401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Log: #137310 - Added class generating wrappers of all JDI methods. These wrappers should catch exceptions thrown from JDI calls.
this issue has been verified recently. Appears as fixed.