-
Bug
-
Resolution: Fixed
-
P4
-
14
-
b24
# java -XX:+UseOSErrorReporting -cp /Volumes/Work/snippets Crasher
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x000000010c115e64, pid=52840, tid=9731
#
# JRE version: Java(TM) SE Runtime Environment (14.0.1+7) (build 14.0.1+7)
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000110d15e64, pid=53519, tid=5891
#
# JRE version: Java(TM) SE Runtime Environment (14.0.1+7) (build 14.0.1+7)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (14.0.1+7, mixed mode, sharing, tiered, compressed oops, g1 gc, bsd-amd64)
# Problematic frame:
# V [libjvm.dylib+0x715e64] _ZN16RawAccessBarrierILy128EE14store_internalILy128EiEEN8EnableIfIXsr12HasDecoratorIXT_EXL_ZL11MO_VOLATILEEEEE5valueEvE4typeEPvT0_+0x4
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /Users/gerard/hs_err_pid53519.log
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
#
# [ timer expired, abort... ]
- blocks
-
JDK-8237727 Mac: after we handle a crash, Apple's crash reporter is left with incorrect state
- Closed
- csr for
-
JDK-8255571 UseOSErrorReporting times out (on Mac and Linux)
- Closed
- is cloned by
-
JDK-8250782 UseOSErrorReporting causes stack space exception (Win)
- Closed
- relates to
-
JDK-6794885 Improve Windows unhandled structured exception reporting - UseOSErrorReporting
- Closed
-
JDK-8251438 Issues with our POSIX set_signal_handler()
- Resolved
-
JDK-4997835 RFE: crash dump will only be created when running w/ -XX:+ShowMessageBoxOnError
- Closed
-
JDK-6227246 Improve Windows unhandled structured exception reporting
- Closed
-
JDK-8237727 Mac: after we handle a crash, Apple's crash reporter is left with incorrect state
- Closed