-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 17, 21, 22
-
Component/s: hotspot
-
b11
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8336801 | 21.0.5 | Thomas Stuefe | P4 | Resolved | Fixed | b01 |
It uses os::is_readable_pointer for readibility check before printing, but that information may be stale once we get to the printing. It would be better to use SafeFetch directly to access the dumped memory location.
- backported by
-
JDK-8336801 os::print_hex_dump is racy
-
- Resolved
-
- relates to
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk/8f28809a
-
Commit(master)
openjdk/jdk21u-dev/0506f4c5
-
Review
openjdk/jdk/14895
-
Review(master)
openjdk/jdk21u-dev/824
(1 links to)