Arch Linux

anykey

Member

From: Trier, Germany

Registered: 2004-06-12

Posts: 79

Java and Eclipse

Hi all,

I am experiencing Segfaults if I try to view an applet with appletviewer. I went on moving to lib32-jdk from AUR, where applets suddenly work, but I cannot execute eclipse from either eclipse or eclipse-bin (from AUR) package anmore. Eclipse won't even start up with it -- it displays a window with "JVM terminated, Exit Code 13" and dies (naturally, if the JVM just died.)

Has anyone succeeded in using lib32-jdk with eclipse on x86_64?

Regards

It would also help to mend the 64bit-JVM to not segfaulting anymore. I am not even sure where to report the segfault -- to Sun or to GNU (it happens with catgets() from glibc). This is all very annoying -- and to top it off, Java bragging about how portable it is -- it isn't as if x86_64 came out just yesterday. This is all ridiculous, some companies not porting stuff over, slowing the progress of the whole industry.

Last edited by anykey (2008-06-20 11:18:36)

anykey

Member

From: Trier, Germany

Registered: 2004-06-12

Posts: 79

Re: Java and Eclipse

Oh, and in case it helps: The segfault with appletviewer is reported as:

#  SIGSEGV (0xb) at pc=0x00007f928032169f, pid=24978, tid=1095833936
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b19 mixed mode linux-amd64)
# Problematic frame:
# C  [libc.so.6+0x3069f]  catgets+0x1f

So I guess the libc team will blame java for being an ass, while any java team will say "libc6 sucks"?

anykey

Member

From: Trier, Germany

Registered: 2004-06-12

Posts: 79

Re: Java and Eclipse

uh... somehow the problem has solved... ITSELF.

After I turned on my machine this morning, it all automagically worked. Maybe this occurs only on even days, or on full moons(??)

Edit: So now I run the normal 64-bit jdk with 64-bit eclipse, and can view and execute applets... strange. If such things keep fixing themselves, let's at least not hope they can "unfix" themselves again.

Last edited by anykey (2008-06-21 11:05:17)