Re: do we need sun.misc.VM?

Date view Thread view Subject view Author view

From: Tim Wilkinson (tim@transvirtual.com)
Date: Sun Nov 15 1998 - 21:01:42 EST

Godmar,

What - Sun break their own 100% compatibility rules - what a shock!!! :-)

Well I think we should create a dummy class for this, and unless anyone
works out what this is supposed to do, we should just keep it as Java only
- after all, what state is it returning and do we have one? Try putting
in a class, returning zero or something and seeing what happens .....

Cheers
Tim

> When running Hotjava, I now (read the email I'm going to send in a few
> minutes!) see this:
>
> Failed to locate native function:
> sun/misc/VM.getState()I
> java.lang.UnsatisfiedLinkError
> at sunw/hotjava/misc/ResourceManager.internalCreate(88)
> at sunw/hotjava/misc/ResourceManager.getManager(80)
> at sunw/hotjava/misc/ResourceManager.create(72)
> at sunw/hotjava/Main.main(144)
>
> So, hotjava is calling into sun.misc?
> As that's supposed to work with every 1.1.x complaint JVM?
>
> Of course, if could be that this ResourceManager of theirs only calls
> into sun/misc/VM under certain (unknown) conditions...
> Note that sun/misc/VM.getState()I is native.
>
> So, shall we implement the native methods of sun/misc/VM.getState()I in
> some kind of compatibility library?
>
> Or shall we ask Sun how come that they rely on sun.misc shit in
> Hotjava?
>
> - Godmar 

--
  Tim Wilkinson                         Tel:     +1 510 704 1660
  Transvirtual Technologies, Inc.,      Fax:     +1 510 704 1893
  Berkeley, CA, USA.                    Email:   tim@transvirtual.com

Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:03 EDT