openjdk team mailing list archive

[Jason Winnebeck <jpwasp@xxxxxxx>]

This issue happened to me on an Atom machine:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0x7) at pc=0x00189377, pid=7397, tid=9845648
#
# Java VM: OpenJDK Client VM (14.0-b08 mixed mode, sharing linux-x86 )
# Distribution: Ubuntu 9.04, package 6b14-1.4.1-0ubuntu11
# Problematic frame:
# C  [libc.so.6+0x79377]  memset+0x37
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid7397.log

At the time this happened, /tmp was full so no file was actually saved.
I think this happened twice in a row but the first time the output was
redirected and I didn't see the JVM report. When I stopped some services
that were holding unlinked files in /tmp keeping it full, the program
ran, but I don't know if that was a coincidence or not.

On this particular system we've been having multiple suspected JVM
crashes. This is the first time I actually got to see the trace. The
program normally runs to logger and I'm not sure why logger wouldn't
pick this up. So, I don't know if this is what's been happening the
whole time.

-- 
A fatal error has been detected by the Java Runtime Environment
https://bugs.launchpad.net/bugs/402617
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: Incomplete

Bug description:
fer@MidasV:~$ java -version
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0x7) at pc=0xb7e2e377, pid=11010, tid=3075840912
#
# Java VM: OpenJDK Client VM (14.0-b08 mixed mode, sharing linux-x86 )
# Distribution: Ubuntu 9.04, package 6b14-1.4.1-0ubuntu10
# Problematic frame:
# C  [libc.so.6+0x79377]  memset+0x37
#
# An error report file with more information is saved as:
# /home/fer/hs_err_pid11010.log
Fallo de segmentación