Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2048546 | 1.4.0 | Btplusnull User | P2 | Closed | Fixed | rc1 |
These tests launch the debuggee VM with -Xdebug -Xnoagent -Djava.compiler=NONE.
This caused the debuggees to run in interpreted mode which was the correct thing
to do before the advent of full speed debugging.
A separate bug has been filed and is being fixed which will cause the
debuggee VM to ignore the -Djava.compiler=NONE option in this case, as
is required by the JPDA spec. This will mean that the debuggees will now
run in the default mode which is -Xmixed. However, many/most/all debuggees
won't actually get compiled because of their transient characteristics.
We need to be able to run the debuggees in -Xcomp mode to assure that
they are compiled and that the tests work in this mode.
This caused the debuggees to run in interpreted mode which was the correct thing
to do before the advent of full speed debugging.
A separate bug has been filed and is being fixed which will cause the
debuggee VM to ignore the -Djava.compiler=NONE option in this case, as
is required by the JPDA spec. This will mean that the debuggees will now
run in the default mode which is -Xmixed. However, many/most/all debuggees
won't actually get compiled because of their transient characteristics.
We need to be able to run the debuggees in -Xcomp mode to assure that
they are compiled and that the tests work in this mode.
- backported by
-
JDK-2048546 jdi regression tests don't adequately test the new full speed debugging feature
-
- Closed
-