-
Enhancement
-
Resolution: Fixed
-
P4
-
11, 17, 20
-
b16
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8314856 | 17.0.9 | Aleksey Shipilev | P4 | Resolved | Fixed | b05 |
Similar to JDK-8217879, the debugging would be easier if we dump more stack in the hex dump. This is especially convenient when debugging Loom and seeing more of the raw stack in the crash log. Reading farther from current SP is generally safe, since stack banging mechanism provides us with accessible stack at all times for normal SPs. In fact, many platforms already read significantly more stack than x86. We can homogenize the stack printing across all architectures.
As the safeguard,JDK-8217994 gives us the facility to read the memory much more safely, so we can dump more stack without elevated risk of secondary crash, in case the stack is not readable.
As the safeguard,
- backported by
-
JDK-8314856 hs_err should print more stack in hex dump
- Resolved
- relates to
-
JDK-8217879 hs_err should print more instructions in hex dump
- Resolved
-
JDK-8217994 os::print_hex_dump should be more resilient against unreadable memory
- Resolved
- links to
-
Commit openjdk/jdk17u-dev/d35a8963
-
Commit openjdk/jdk/cbd0688b
-
Review openjdk/jdk17u-dev/1677
-
Review openjdk/jdk/10282
(2 links to)