Two problems --
First, the following RuntimeExceptions are spec'ed to be thrown in only
some of the places where they can be:
ObjectCollectedException
VMDisconnectedException
VMMismatchException
VMOutOfMemoryException
NullPointerException
Spec should be consistent.
Second, some exceptions (specifically, ObjectCollectedException
and VMDisconnectedException) are not always thrown by methods which
are spec'ed to throw them. Exception is not thrown because no
interaction with target VM is needed (e.g., info is cached).
They should be specified that the exception "may" be thrown.
First, the following RuntimeExceptions are spec'ed to be thrown in only
some of the places where they can be:
ObjectCollectedException
VMDisconnectedException
VMMismatchException
VMOutOfMemoryException
NullPointerException
Spec should be consistent.
Second, some exceptions (specifically, ObjectCollectedException
and VMDisconnectedException) are not always thrown by methods which
are spec'ed to throw them. Exception is not thrown because no
interaction with target VM is needed (e.g., info is cached).
They should be specified that the exception "may" be thrown.
- duplicates
-
JDK-4464724 /nsk/jdi tests throw NullPointerException- jdi.Connector.BooleanArgument.isValid
- Closed
-
JDK-4331535 JDI: some VirtualMachine methods do not throw VMDisconnectedException
- Closed
-
JDK-4394613 JDI spec: ReferenceType.equals() does not throw any Exception for unloaded class
- Closed
-
JDK-4432051 JDI spec: methods which throw NullPointerException on null param not documented
- Closed