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 a number of JVMTI functions not used in JDWP agent. They are targeted for profiling support and will not be tested with JDWP tests. But they can be tested with any Java profiler, for example new JVMTI profiler in Eclipse TPTP project [1]. Their automation testing framework can be used for testing JVMTI profiling support in Harmony JRE. Ivan. [1] http://www.eclipse.org/tptp/ On 10/4/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
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 topic for discussion. Yah, I've been noting that in JVMTI commit messages - we need a suite of JVMTI tests, and I guess we can use the agent for it? geir --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
