← Back to team overview

openjdk team mailing list archive

[Bug 614680] [NEW] game colonisation crash due to java runtime error

 

Public bug reported:

see also bug    #349596, but my consolse output is a little different:

Disabling IPV6 network stack to work around bug #560056 on openjdk
If you experience problems with connecting to remote servers, 
you can put it back by running Freecol this way:
  freecol --enable-ipv6
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f011bac7fb6, pid=2078, tid=139642290108176
#
# JRE version: 6.0_18-b18
# Java VM: OpenJDK 64-Bit Server VM (16.0-b13 mixed mode linux-amd64 )
# Derivative: IcedTea6 1.8
# Distribution: Ubuntu 10.04.1 LTS, package 6b18-1.8-4ubuntu3
# Problematic frame:
# V  [libjvm.so+0x5d9fb6]
#
# An error report file with more information is saved as:
# /home/christoph/hs_err_pid2078.log
[thread 139642291160848 also had an error]

** Affects: openjdk-6 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
game colonisation crash due to java runtime error
https://bugs.launchpad.net/bugs/614680
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-6 in ubuntu.

Status in “openjdk-6” package in Ubuntu: New

Bug description:
see also bug  	#349596, but my consolse output is a little different:

Disabling IPV6 network stack to work around bug #560056 on openjdk
If you experience problems with connecting to remote servers, 
you can put it back by running Freecol this way:
  freecol --enable-ipv6
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f011bac7fb6, pid=2078, tid=139642290108176
#
# JRE version: 6.0_18-b18
# Java VM: OpenJDK 64-Bit Server VM (16.0-b13 mixed mode linux-amd64 )
# Derivative: IcedTea6 1.8
# Distribution: Ubuntu 10.04.1 LTS, package 6b18-1.8-4ubuntu3
# Problematic frame:
# V  [libjvm.so+0x5d9fb6]
#
# An error report file with more information is saved as:
# /home/christoph/hs_err_pid2078.log
[thread 139642291160848 also had an error]





Follow ups

References