调试libjvm.so中的SIGSEGV Java致命错误

本文介绍了调试libjvm.so中的SIGSEGV Java致命错误的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我正试图在Centos 5.7流浪盒中运行码头（它在真正的计算机上运行良好;用centos和linux mint测试）。这是标题错误：

I'm trying to run jetty inside a Centos 5.7 vagrant box (it runs fine on "real" computers; tested with centos and linux mint). This is the header error:

# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00002abb2551a8b1, pid=4299, tid=1105414464 # # JRE version: 6.0_37-b06 # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.12-b01 mixed mode linux-amd64 ) # Problematic frame: # V [libjvm.so+0x87a8b1] YieldingFlexibleWorkGang::start_task(YieldingFlexibleGangTask*)+0x11 # # An error report file with more information is saved as: # /usr/local/jetty-7.6.7/bin/hs_err_pid4299.log # # If you would like to submit a bug report, please visit: # java.sun/webapps/bugreport/crash.jsp # Aborted

我在这里粘贴了日志： raw.github/gist/4067152/3ce91df20828ba1d83271aacbc56c985a4e22ab1/gistfile1.txt

I've pasted the log here: raw.github/gist/4067152/3ce91df20828ba1d83271aacbc56c985a4e22ab1/gistfile1.txt

我正试图获得一些提示。 :)已经在 bugs.sun/ 上搜索了google和bug数据库。

I'm trying to get some hints. :) Already searched google and the bug database at bugs.sun/.

谢谢！

推荐答案

如果你能够轻松复制，你应该配置系统以创建核心转储。

If you are able to reproduce this easily, you should configure your system to create a core dump.

使用 ulimit -c unlimited 将使您的系统能够生成这样的转储到下一个 SIGSEGV 事件。一旦创建了核心转储文件，您就可以使用 gdb 来检查它。

Using ulimit -c unlimited will enable your system to produce such a dump on the next SIGSEGV event. Once the core dump file will be created you will be able to examine it, using gdb.

参见确定崩溃发生的位置，了解用于确定原因的选项的详细信息。

See Determining Where the Crash Occurred for details on what options to use to determine the cause.