I recently (well, one week ago) moved from i386 to amd64 on my machine.
Before the re-install Eclipse worked 1a (used JDK 1.4.2, however). After
the re-install I cvsupped to 6.0-STABLE, performed a build-/
installworld, cvsupped ports and ran "portupgrade -fa". I had to compile
Eclipse using WITHOUT_CAIRO, as it didn't link properly against the
cairo-Libs. Java 1.5 compiled fine - as the "WITHOU_WEB" is being turned
on automagically on amd64...
Well, with amd64 I don't have JDK 1.4.2 any longer and so use 1.5.
Unfortunately, Eclipse always crashes with with a Signal 6 shortly after
starting up and compiling the Workspace (used to pull a project from
CVS). My first "action" was to remove .eclipse - however, that didn't
Now, I read some hints regarding libz.so - Problems here in the list.
However, the JDK 1.5 I installed is "jdk-1.5.0p2_3" - and if I got the
(latest) commit-comment right, that JDK should not show these
libz-Problems any longer (btw: Eclipse it @ "eclipse-3.1.1_2")?!
Does anyone have a hint? The crash always happens in "Java indexing"; I
enclosed one hs_err - File...
0x00000000007dec00 VMThread [id=8325120]
0x0000000000520c00 WatcherThread [id=8879104]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
def new generation total 39424K, used 33347K [0x0000000845910000,
eden space 35072K, 82% used [0x0000000845910000, 0x0000000847560f10,
from space 4352K, 100% used [0x0000000847b50000, 0x0000000847f90000,
to space 4352K, 0% used [0x0000000847f90000, 0x0000000847f90000,
tenured generation total 87424K, used 73301K [0x000000084ae60000,
the space 87424K, 83% used [0x000000084ae60000, 0x000000084f5f54b0,
compacting perm gen total 32128K, used 31992K [0x0000000855910000,
the space 32128K, 99% used [0x0000000855910000, 0x000000085784e288,
No shared spaces configured.