In article <20030808073728.GB11860@rostock.zgdv.de>,
Dirk Ruediger <dgrue@web.de> wrote:

A current kernel, as of today will work correctly for all jvms < 1.4.2 and
kernels that are configured to have:

makeoptions     TEXTADDR=d0100000 
options         KERNBASE_LOCORE=0xd0000000  

java 1.4.2 is not yet working.

christos

>-=-=-=-=-=-
>
>On Thu, 07 Aug 2003, Jaromir Dolecek wrote:
>
>> > Heap at VM Abort:
>> > Heap
>> > ^C
>> 
>> Hmm, did you try upping your resource limits? Particularily
>> stack and data limits. 'ulimit -s 8192' might get you
>> a bit further.
>Nope. I had stack size defined with 32768 kbytes.
>
>drue@ash[9:31]~/projects/jaxb :2 27> echo $JAVA_HOME
>/usr/pkg/java/sun-1.4.2/
>drue@ash[9:31]~/projects/jaxb :2 28> limit
>cputime         unlimited
>filesize        unlimited
>datasize        786432 kbytes
>stacksize       32768 kbytes
>coredumpsize    unlimited
>memoryuse       1017764 kbytes
>descriptors     64 
>memorylocked    339254 kbytes
>maxproc         160 
>drue@ash[9:32]~/projects/jaxb :2 33> java -version
>#
># 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-b28 mixed mode)
>#
># Error ID: 4F533F4C494E55580E43505001C9
>#
>
>Heap at VM Abort:
>Heap
>
>Same procedure as every time :-/
>The box has physically 1GB main memory. And these limits work for jdk131
>etc (even for eclipse and an meory-consuming obfuscator ;-).
>
>Regards
>Dirk
>-- 
>Dirk Ruediger, Rostock, Germany
> 
>Computers are useless.  They can only give you answers.
>                -- Pablo Picasso
>
>-=-=-=-=-=-
>[Attachment type=text/x-vcard, name=drue.vcf]
>-=-=-=-=-=-