[Solved] Java Runtime error when I run a .jar file

[Dennola4]

OS: Salix 13.1
JRE version: 6.0_20-b02
Source file: $ wget http://files.gokgs.com/javaBin/cgoban.jar

New problem, started recently:

When I attempt to launch a program which normally works fine I get this message:

Code: Select all

dennis[~]$ java -jar /home/dennis/Downloads/cgoban_d/cgoban.jar
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0x7) at pc=0xb770980e, pid=8149, tid=3067767664
#
# JRE version: 6.0_20-b02
# Java VM: Java HotSpot(TM) Client VM (16.3-b01 mixed mode, sharing linux-x86 )
# Problematic frame:
# C  [libc.so.6+0x7b80e]  memset+0x3e
#
# An error report file with more information is saved as:
# /home/dennis/hs_err_pid8149.log
Segmentation fault

.....resulting in this error report:

Code: Select all

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0x7) at pc=0xb766980e, pid=8126, tid=3067112304
#
# JRE version: 6.0_20-b02
# Java VM: Java HotSpot(TM) Client VM (16.3-b01 mixed mode, sharing linux-x86 )
# Problematic frame:
# C  [libc.so.6+0x7b80e]  memset+0x3e
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

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

Current thread is native thread

siginfo:si_signo=SIGBUS: si_errno=0, si_code=2 (BUS_ADRERR), si_addr=0xb6c81000

If I reboot then it works, but after awhile I'll try to open it and get this message. Any idea what is going on and how to fix it? Thanks.

EDIT: I just discovered that clearing my temp files makes it run properly again. Still, if there is obviously something I could do to fix this rather than getting error messages and clearing temp files as a solution please let me know, otherwise I'll just mark the thread solved.

[Dennola4]

Ok, so I'll assume that clearing temp files is the solution and that there is nothing else going on. That is, unless a Salix dev or someone else qualified to call themselves a *Salix Wizard* would like to enlighten this thread with a constructive insight. Otherwise I'm marking the problem solved and closing the thread. Thanks.



Dennis in New Orleans

[Shador]

This is a quite low-level error, which I never saw myself. Actually something like this should never happen: https://en.wikipedia.org/wiki/SIGBUS
It seems to happen in glibc, but it also seems to be closely tied to Java or the way java uses those system calls. And then it seems to be triggered only by that specific/some specific programs. I don't think there's much that can be done but somebody fucked up cgoban, Oracle/Sun, glibc devs, kernel devs, ... And it probably happens only on certain hardware/software/hardware-software combinations.

Chances are so small to pinpoint this and the amount of work so big, that given the scope it doesn't seem worth it. You're of course welcome to run this code:

Code: Select all

extern void *magicskillz(void *hint); // ask the inventor of the "eierlegende wollmilchsau" for the function body

report((culprit *) magicskillz(NULL));

I think that sums it up quite well.

[mimosa]

Surely the "eierlegende Wollmilchsau" is a Microsoft product? Linux livestock do one thing, well ... nicht wahr?

[Shador]

Surely the "eierlegende Wollmilchsau" is a Microsoft product? Linux livestock do one thing, well ... nicht wahr?

I know of no good translation, but it's close to a swiss-army-knife or million-gadget device. A utopian, ubiquitous device that can do everything. Sometimes it also has the insinuation of unifying too many features in one object. But that's not primarly intended here. Literally it's an egg-laying, wool and milk yielding pig.
But you probably know that already.

[Dennola4]

Shador,

I sort of figured that the culprit rested somewhere in (presumably) some weird code in one of the packages and was not in fact a system error reflecting a corrupted OS. Thanks for the response. "Egg-laying wool-milk-sow" indeed. HAH!

Dennis in New Orleans

[Shador]

I sort of figured that the culprit rested somewhere in (presumably) some weird code in one of the packages and was not in fact a system error reflecting a corrupted OS.

It could be anywhere. Thus hint = NULL.