Hi,

Could you, please, review the following test-only change (adding a new test):

CR: https://bugs.openjdk.java.net/browse/JDK-8148103
Webrev: http://cr.openjdk.java.net/~akulyakh/8148103_02/

The new test verifies the new JDWP commands: AllModules, Module, Name, 
ClassLoader, CanRead.

It does so by launching a debuggee java program  with the necessary 
JDWP-related options, so that a JDWP session can be established between the 
debuggee and the test.

When started the debuggee reports its loaded modules to the test.
The test then initiates the JDWP session and issues AllModules command to get 
the modules info by means of the JDWP.
For each module the test issues Name command. It then verifies that the modules 
names reported via the JDWP are the same as reported by the debuggee using the 
Java API.
Additionally, for each module the test issues CanRead and Classloader commands 
and verifies that the corresponding replies are correct.

Since all the previous JDWP tests were implemented using the deprecated closed 
test framework, the amount of the code for this test is slightly larger than 
usually for a single test.
The simple JDWP framework, created for this test, allows for porting the other 
JDWP tests to the jtreg in the same manner.

Best regards,
Alexander

Reply via email to