-
Bug
-
Resolution: Fixed
-
P4
-
11, 17, 21, 22, 23
-
b22
-
x86
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8350910 | 21.0.8-oracle | Calvin Cheung | P4 | Resolved | Fixed | master |
| JDK-8334004 | 21.0.5 | Martin Doerr | P4 | Resolved | Fixed | b01 |
| JDK-8339973 | 17.0.14 | Martin Doerr | P4 | Resolved | Fixed | b01 |
/jdk/src/hotspot/share/prims/unsafe.cpp:162:38: runtime error: applying non-zero offset 4563897424 to null pointer
#0 0x10e37a724 in index_oop_from_field_offset_long(oop, long) unsafe.cpp:162
#1 0x10e37ba9e in MemoryAccess<long>::addr() unsafe.cpp:216
#2 0x10e37bbb9 in MemoryAccess<long>::get_volatile() unsafe.cpp:257
#3 0x10e370f28 in Unsafe_GetLongVolatile(JNIEnv_*, _jobject*, _jobject*, long) unsafe.cpp:343
#4 0x12e425f0d (<unknown module>)
#5 0x12e41f22b (<unknown module>)
#6 0x12e41f22b (<unknown module>)
Adding a big offset to nullptr seems to be detected as an issue.
- backported by
-
JDK-8334004 unsafe.cpp:162:38: runtime error in index_oop_from_field_offset_long - applying non-zero offset 4563897424 to null pointer
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk21u-dev/e716aaec
-
Commit
openjdk/jdk/23a72a1f
-
Commit(master)
openjdk/jdk17u-dev/98586bbd
-
Review
openjdk/jdk21u-dev/685
-
Review
openjdk/jdk/19087
-
Review(master)
openjdk/jdk17u-dev/2854