JVM 崩溃报错 SIGSEGV (0xb) 是什么原因？

来到golang学习网的大家，相信都是编程学习爱好者，希望在这里学习文章相关编程知识。下面本篇文章就来带大家聊聊《JVM 崩溃报错 SIGSEGV (0xb) 是什么原因？》，介绍一下，希望对大家的知识积累有所帮助，助力实战开发！

jvm crash 报错 sigsegv (0xb) 分析原因

在分析 jvm crash 错误 sigsegv (0xb) 时，我们遇到了以下 hs_err_pidxxx.log 文件：

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f5e94bd20a7, pid=752, tid=140036367759104
#
# JRE version: Java(TM) SE Runtime Environment (8.0_60-b27) (build 1.8.0_60-b27)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0x6340a7]  IfNode::up_one_dom(Node*, bool)+0x97
#
# Core dump written. Default location: /home/admin/core or core.752
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

---------------  T H R E A D  ---------------

Current thread (0x00007f5e9050e000):  JavaThread "C2 CompilerThread7" daemon [_thread_in_native, id=942, stack(0x00007f5cc1e4b000,0x00007f5cc1f4c000)]

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x000000000000002c

Registers:
RAX=0x00007f5c80ec2780, RBX=0x00007f5c80a98a38, RCX=0x0000000000000000, RDX=0x0000000000000000
RSP=0x00007f5cc1f46c70, RBP=0x00007f5cc1f46c70, RSI=0x0000000000000000, RDI=0x00007f5c806141f8
R8 =0x0000000000000fbc, R9 =0x0000000000000001, R10=0x0000000000000001, R11=0x00007f5cc1f49bf0
R12=0x00007f5c80ab2418, R13=0x00007f5cc1f47a00, R14=0x0000000000000000, R15=0x00007f5c806141f8
RIP=0x00007f5e94bd20a7, EFLAGS=0x0000000000010246, CSGSFS=0x002b000000000033, ERR=0x0000000000000004
  TRAPNO=0x000000000000000e

Top of Stack: (sp=0x00007f5cc1f46c70)
0x00007f5cc1f46c70:   00007f5cc1f46f00 00007f5e94bd374d
0x00007f5cc1f46c80:   00007f5cc1f46cb0 00007f5e94e87972
0x00007f5cc1f46c90:   00007f5cc1f46cd0 00007f5e94e88016
0x00007f5cc1f46ca0:   00007f5cc1f47a00 00007f5c00000000
0x00007f5cc1f46cb0:   00007f5c80ab4138 0000007c00000017
0x00007f5cc1f46cc0:   00007f5cc1f47a00 00007f5e94f03dc0
0x00007f5cc1f46cd0:   00007f5c80ab2480 00007f5c80ab2500
0x00007f5cc1f46ce0:   0000000000000001 00007f5e9050e460
0x00007f5cc1f46cf0:   00007f5c00000001 00007f5cc1f483d8
0x00007f5cc1f46d00:   00007f5cc1f46d40 00007f5e94e88016
0x00007f5cc1f46d10:   00007f5cc1f483f8 00007f5c80ab4470
0x00007f5cc1f46d20:   0000000000000000 0000000000000001
0x00007f5cc1f46d30:   00007f5c80ab4470 00007f5cc1f47a00
0x00007f5cc1f46d40:   00007f5cc1f46db0 00007f5e94f019dc
0x00007f5cc1f46d50:   00007f5c80ce3160 00007f5cc1f48380
0x00007f5cc1f46d60:   00007f5cc1f46db0 00007f5cc1f483d8
0x00007f5cc1f46d70:   00007f5cc1f48380 00007f5cc1f48418
0x00007f5cc1f46d80:   00007f5cc1f483f8 00007f5c80ab3588
0x00007f5cc1f46d90:   00007f5c80ce3160 0000000000000001
0x00007f5cc1f46da0:   00007f5c80ce3478 00007f5c80ab4470
0x00007f5cc1f46db0:   00007f5c80ab2138 00007f5c80ab2180

文中关于的知识介绍，希望对你的学习有所帮助！若是受益匪浅，那就动动鼠标收藏这篇《JVM 崩溃报错 SIGSEGV (0xb) 是什么原因？》文章吧，也可关注golang学习网公众号了解相关技术文章。