-
Bug
-
Resolution: Fixed
-
P4
-
11, 12, 13, 14
If JFR is running when JVM crashes, JFR will dump data to hs_err_pid<PID>.jfr . It would perform in prepare_for_emergency_dump(). However this function transits thread state to "_thread_in_vm".
If the crash occurs in JNI code, we cannot see some messages in hs_err log.
* With -XX:StartFlightRecording
```
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
```
* Without -XX:StartFlightRecording
```
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
```
We can reproduce it as below:
1. Clone reproducer
$ git clone https://github.com/YaSuenag/garakuta.git
2. Build reproducer
$ cd garakuta/NativeSEGV
$ make JAVA_HOME=/path/to/jdk
3. Run reproducer
$ java -XX:StartFlightRecording -Djava.library.path=. NativeSEGV
If the crash occurs in JNI code, we cannot see some messages in hs_err log.
* With -XX:StartFlightRecording
```
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
```
* Without -XX:StartFlightRecording
```
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
```
We can reproduce it as below:
1. Clone reproducer
$ git clone https://github.com/YaSuenag/garakuta.git
2. Build reproducer
$ cd garakuta/NativeSEGV
$ make JAVA_HOME=/path/to/jdk
3. Run reproducer
$ java -XX:StartFlightRecording -Djava.library.path=. NativeSEGV
- relates to
-
JDK-8233706 JFR emergency dump should be performed after error reporting
-
- Resolved
-