-
Type:
Enhancement
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 20
-
Component/s: hotspot
-
b18
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8300703 | 17.0.7-oracle | Calvin Cheung | P3 | Resolved | Fixed | b04 |
| JDK-8301335 | 17.0.7 | Goetz Lindenmaier | P3 | Resolved | Fixed | b01 |
Try to recover and output meaningful information in more situations, such as:
- when a pointer is in Method metadata memory range, but the memory is not committed
- when we call a bad address
When calling a bad address, we usually don't get a meaningful stack backtrace, but in many situations we can if we know where to find the caller information.
- when a pointer is in Method metadata memory range, but the memory is not committed
- when we call a bad address
When calling a bad address, we usually don't get a meaningful stack backtrace, but in many situations we can if we know where to find the caller information.
- backported by
-
JDK-8300703 misc crash dump improvements
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8307549 AsyncGetCallTrace crashes on Mac M1 after JDK-8294160
-
- Closed
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk17u-dev/7fa6bc2f
-
Commit
openjdk/jdk/6f8f28e7
-
Review
openjdk/jdk17u-dev/1107
-
Review
openjdk/jdk/10387
(3 links to)