CODEWITHSUNDEEP
javajvm
Favio
Favio

Reputation: 1009

Debugging SIGSEGV Java Fatal Error in libjvm.so

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:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted

I've pasted the log here: https://gist.github.com/favrik/4067152

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

Thanks!

Upvotes: 6

Views: 15351

Answers (1)

dan
dan

Reputation: 13262

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

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.

Upvotes: 5

Related Questions