Unintentional abort with SIGUSR2
takao.shinji at lab.ntt.co.jp
Tue Mar 14 07:03:51 UTC 2017
I encountered an unintentional process abort with SIGSEGV
when a Java process received a SIGUSR2.
I was little surprised because I believed that the SIGUSR2
was to be ignored when it had no user definition.
Is there any documentation for the behavior?
# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x00007fca804a40a2, pid=2137, tid=0x00007fca81949740
# JRE version: OpenJDK Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
# Java VM: OpenJDK 64-Bit Server VM (25.121-b13 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0x8700a2]
# Core dump written. Default location: /xxx/xxx/core or core.2137
# If you would like to submit a bug report, please visit:
--------------- T H R E A D ---------------
Current thread is native thread
siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x0000000000000110
More information about the core-libs-dev