Re: linux JDK with compat_linux broken

On Thu, Aug 19, 2004 at 02:06:24PM -0700, Vitaly Markitantov wrote:
> In not so old -CURRENT (from August 18 2004) doesn't work linux's JDK from
> ports linux-sun-jdk-1.4.2.05
> 
> When i run simple
> $/usr/local/linux-sun-jdk1.4.2/bin/java -version
> Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location
> #
> # HotSpot Virtual Machine Error, Internal Error
> # Please report this error at
> # http://java.sun.com/cgi-bin/bugreport.cgi
> #
> # Java VM: Java HotSpot(TM) Client VM (1.4.2_05-b04 mixed mode)
> #
> # Error ID: 4F533F4C494E55583F491418160E435050035E
> #
> # Problematic Thread: prio=-1086328344 tid=0x08090d40 nid=0x736b runnable
> #
> 
> Heap at VM Abort:
> Heap
>  def new generation   total 576K, used 0K [0x2c7a0000, 0x2c840000, 0x2cc80000)
>   eden space 512K,   0% used [0x2c7a0000, 0x2c7a0048, 0x2c820000)
>   from space 64K,   0% used [0x2c820000, 0x2c820000, 0x2c830000)
>   to   space 64K,   0% used [0x2c830000, 0x2c830000, 0x2c840000)
>  tenured generation   total 1408K, used 0K [0x2cc80000, 0x2cde0000, 0x307a0000)
>    the space 1408K,   0% used [0x2cc80000, 0x2cc80000, 0x2cc80200, 0x2cde0000)
>  compacting perm gen  total 4096K, used 277K [0x307a0000, 0x30ba0000,
> 0x347a0000)
>    the space 4096K,   6% used [0x307a0000, 0x307e56c0, 0x307e5800, 0x30ba0000)
> 
> 
> When linprocfs mounted java gets 100% cpu time and hangs, till i say
> $killall -9 java
> 
> It's bad, because i need this linux-sun-jdk-1.4.2.05 to build native BSD JDK.

I'm looking into this, but I can't seem to reproduce the problem here
with J2RE 1.4.2 (I'm still in the process of downloading the SDK).

When linprocfs is not mounted:
$ ./java -version
Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)

When linprocfs is mounted:
$ ./java -version
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)

Can you confirm that the problem still exists after updating your sources
and rebuilding the kernel and all relevant modules?


Tim