I'm submitting this per a conversation earlier today with gri and kbr.
HotSpot needs to deal more gracefully with SIGSEGV, SIGBUS, and similar OS
events that occur when an unsafe get or put operation accesses invalid memory.
Whether such an invocation returns zero, returns an arbitrary value, or throws
an exception doesn't really matter -- the important thing is to avoid crashing
the VM.
This is required by NIO in order to support memory-mapped files.
I'm filing related bugs under both C1 and C2.
-- mr@eng 2001/5/3
HotSpot needs to deal more gracefully with SIGSEGV, SIGBUS, and similar OS
events that occur when an unsafe get or put operation accesses invalid memory.
Whether such an invocation returns zero, returns an arbitrary value, or throws
an exception doesn't really matter -- the important thing is to avoid crashing
the VM.
This is required by NIO in order to support memory-mapped files.
I'm filing related bugs under both C1 and C2.
-- mr@eng 2001/5/3
- duplicates
-
JDK-4454115 Need to deal gracefully with unsafe operations that access invalid memory (C2)
-
- Resolved
-
- relates to
-
JDK-6244515 Unsafe operations that access invalid memory are not handled gracefully
-
- Closed
-
-
-
- Closed
-