JDK-8151560 : Safepoint logging has mismatch between command line level and printed level
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2016-03-09
- Updated: 2016-04-21
- Resolved: 2016-03-18
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 9 |
|---|
9 b115Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
-Xlog:safepoint=trace reveals "debug"-level logging that -Xlog:safepoint=debug does not. Probably due to a mismatch between an if statement and a logging statement in the source code.
Comments
|