I figured it out. I was running the right *java*, but I was running the rmiregistry from
libgcj.
Tom Ball wrote:
All I had to do was change my PATH setting so that the 1.4.1 version of
Java came before the libgcj one. I haven't tested everything yet, but
so far, so good...
Tom
On Mon, 2002-11
All I had to do was change my PATH setting so that the 1.4.1 version of
Java came before the libgcj one. I haven't tested everything yet, but
so far, so good...
Tom
On Mon, 2002-11-04 at 17:15, Joseph Shraibman wrote:
> I tried to run java 1.4.1 from sun on my rh 8.0 box and I spent a day trying
John,
You can run "/usr/bin/strings core" to get some info from the core file.
I have been doing Java development daily on a Mandrake 8.2 system for
several months. Glibc version is 2.2.4, but I continuously move to the
latest versions of the Blackdown JVM (currently 1.4.1 beta) so it's been
I had been running Blackdown 1.3.1-FCS (green threads, nojit) without
any problems for over a year on a system with Linux Kernel version
2.2.16 and Glibc 2.2.4 on a Red Hat Linux 7.0 base. I've been using the
"ulimit -s 2048" setting to avoid the problem that caused segmentation
violations ear
