-
Bug
-
Resolution: Fixed
-
P4
-
7
-
b20
-
generic
-
generic
When a com/sun/jdi test is run, if options are to be passed to the debuggee VM, they have to be placed in a file named @debuggeeVMOptions by the caller of jtreg. The jdi test infrastructure extracts the options from this file and uses them in the launching of the debuggee. The reason for this is that jtreg did not support a mechanism for doing this.
Newer versions of jtreg, eg, 3.2.2 allow arbitrary options to be passed to the program under test in -vmoptions.
We should define a property, eg jdi.debuggee.VMoptions, into which debuggee VM options can be placed by the caller of jtreg and from which the test infrastructure can get those options and use them in the launching of the debuggee VM.
EG, a jtreg caller could do
jtreg .... -vmoption:'-Djdi.debuggee.VMoptions="-server -Xcomp"'
Newer versions of jtreg, eg, 3.2.2 allow arbitrary options to be passed to the program under test in -vmoptions.
We should define a property, eg jdi.debuggee.VMoptions, into which debuggee VM options can be placed by the caller of jtreg and from which the test infrastructure can get those options and use them in the launching of the debuggee VM.
EG, a jtreg caller could do
jtreg .... -vmoption:'-Djdi.debuggee.VMoptions="-server -Xcomp"'
- relates to
-
JDK-8048892 TEST_BUG: shell script tests need to be change to not use retired @debuggeeVMOptions mechanism
-
- Resolved
-
- links to
-
Review(master) openjdk/jdk8u-dev/492