Yes, JDWP agent uses most of JVMTI functions, and testing JDWP level
indirectly checks JVMTI implementation. JDWP unit tests included into
JDWP contribution do not provide exhaustive testing, but they often
catch problems with basic JVMTI support related to debug
functionality.
However, there is
Initially I considered putting JDWP agent to classlib as part of JPDA
module, so its build is adjusted to the classlib build structure. But
I agree that putting it to tools directory (or to jdktools as
discussed in separate thread) should be better solution. JDWP agent is
not an implementation of
Ivan Popov wrote:
--- I'd like to see JDWP unit tests included into regular tests runs,
they often reveal problems with JVMTI and JNI support when JVM
implementation is changed. I'm not sure that unit tests are provided
with other tools and included into tests run, and this can be a
separate
Keeping the discussion out of the vote thread.
Both this and javah aren't going into classlib anyway. I was going
to suggest we put them into /tools, bring the javac and keytool over,
and I volunteer to do it. Then add that to the federated build, and
get into the jdk.
geir
On Sep 28,
