-
Bug
-
Resolution: Fixed
-
P4
-
openjdk8u322
-
master
-
generic
-
windows
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8288479 | openjdk8u352 | Alex Kasko | P4 | Resolved | Fixed | master |
Consider the following command in 8u:
java -Xmx4g -XX:+PrintFlagsFinal -version
Its output on Windows will contain invalid zero values for 64-bit flags which actual values are exact multiple of 4 GiB:
...
uintx MaxHeapSize := 0
...
This happens because value is stored in uintx (uintptr_t) that is 64-bit, but "%-16lu" formatting string is used that is intended for unsigned long (32-bit on Windows).
Actual flag value is correct, the problem happens when this value is being formatted for the output.
This problem was fixed in 9 as part ofJDK-8042893 .
java -Xmx4g -XX:+PrintFlagsFinal -version
Its output on Windows will contain invalid zero values for 64-bit flags which actual values are exact multiple of 4 GiB:
...
uintx MaxHeapSize := 0
...
This happens because value is stored in uintx (uintptr_t) that is 64-bit, but "%-16lu" formatting string is used that is intended for unsigned long (32-bit on Windows).
Actual flag value is correct, the problem happens when this value is being formatted for the output.
This problem was fixed in 9 as part of
- backported by
-
JDK-8288479 Incorrect PrintFlags formatting on Windows
-
- Resolved
-
- relates to
-
JDK-8288020 Possible 8u backport of PRAGMA_FORMAT_MUTE_WARNINGS_FOR_GCC changes
-
- Open
-
-
-
- Resolved
-
(2 links to)