-
Bug
-
Resolution: Fixed
-
P3
-
9-repo-verona
-
team
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8144369 | 9 | Alejandro Murillo | P3 | Resolved | Fixed | b95 |
Bundle names will be modified to align with the existing “debuginfo” and “fastdebug” bundle names. We will introduce a new VM system property “java.vm.debug” which propagates the build’s existing DEBUGLEVEL (“release”, “fastdebug”, “slowdebug”, “optimized”). The “debugness” of a build will be printed out by the launcher in all cases except when it’s “release”, e.g.:
java.vm.debug = (“foo” != “release”)
$java -version
java version "9-ea"
Java(TM) SE Runtime Environment (foo build 9-ea+88)
Java HotSpot(TM) 64-Bit Server VM (foo build 9-ea+88, mixed mode)
java.vm.debug = “release”:
$java -version
java version "9-ea"
Java(TM) SE Runtime Environment (build 9-ea+88)
Java HotSpot(TM) 64-Bit Server VM (build 9-ea+88, mixed mode)
It may be necessary to update regression tests to use the system property to determine the debug level.
java.vm.debug = (“foo” != “release”)
$java -version
java version "9-ea"
Java(TM) SE Runtime Environment (foo build 9-ea+88)
Java HotSpot(TM) 64-Bit Server VM (foo build 9-ea+88, mixed mode)
java.vm.debug = “release”:
$java -version
java version "9-ea"
Java(TM) SE Runtime Environment (build 9-ea+88)
Java HotSpot(TM) 64-Bit Server VM (build 9-ea+88, mixed mode)
It may be necessary to update regression tests to use the system property to determine the debug level.
- backported by
-
JDK-8144369 Store debug level in jdk.debug and conditionally print in "java -version"
- Resolved
- relates to
-
JDK-8139951 Do not store debug level in OPT part of Verona string
- Resolved