Kaffe and HotJava
EP510777 at exchange.FRANCE.NCR.com
Tue Nov 10 08:39:31 PST 1998
I remove my traces from java.lang.System in the
patch kaffe-hj.diff, you should read this line:
+ if (s != null)
and not this line
+ if (security != null)
> -----Original Message-----
> From: Parmelan, Edouard
> Sent: Tuesday, November 10, 1998 4:44 PM
> To: 'Godmar Back'
> Cc: 'kaffe at rufus.w3.org'
> Subject: Kaffe and HotJava
> Hi Godmar,
> Hi Everybody,
> I try to run HotJava 1.1.4 with kaffe.
> I need two small patches:
> - It seems that HotJava extends class java.util.Properties
> and defines a get() method that calls getProperty().
> But getProperty() calls get() not super.get().
> - HotJava can't set his own SecurityManager so it call
> System.setSecurityManager() with null. Unfortunary, many
> kaffe classes assumes that the getSecurityManager() is not null.
> As kaffe use a private defaultSecurityManager called
> NullSecurityManager, setSecurityManager(null) don't change the
> default one.
> The patch kaffe-hj.diff contains this two small patches.
> Now, HotJava starts and shows a DeadLock with processClass()...
> The patch kaffe-deadlock.diff add some debuging traces.
> Godmar, could you analyse this repeatable deadlock ?
> << File: kaffe-hj.diff >>
> << File: kaffe-deadlock.diff >>
More information about the kaffe