IcedTea6-plugin PluginAppletSecurityContext NullPointers

Deepak Bhole dbhole at redhat.com
Thu Feb 12 09:18:14 PST 2009


* Deepak Bhole <dbhole at redhat.com> [2009-02-12 12:16]:
> * Xerxes Rånby <xerxes at zafena.se> [2009-02-12 05:37]:
> > Xerxes Rånby wrote:
> >> Hello oliver!
> >>
> >> Oliver May wrote:
> >>> Hi all!
> >>>
> >>> I am having some difficulties with icedtea-6-plugin on debian (armel). I 
> >>> am working on a java applet for communication between a browser 
> >>> (iceweasel) and hardware (gpsd) on the neo freerunner phone.
> >>>
> >> Do you have a url to this applet and its sourcecode? without it it is 
> >> really hard to see whats going on.
> >> It would be great if you happen to have a small testcase based on code 
> >> from the applet that exposes this bug so that it can be fixed properly on  
> >> ARM armel platforms.
> >>> The problem lies mainly in the communication between the browser and the 
> >>> applet, I am calling java methods from javascript code. Whenever I try to 
> >>> call a method on a java object I get following errors:
> >>>
> >>> java.lang.NullPointerException:
> >>>     at 
> >>> sun.applet.PluginAppletSecurityContext.checkPermission(PluginAppletSecurityContext.java:1002)
> >>>     at 
> >>> sun.applet.PluginAppletSecurityContext.handleMessage(PluginAppletSecurityContext.java:658)
> >
> > Deepak where do the PluginDebug.debug post its debug messages? It might 
> > shine some light on what calling method is used on what object in 
> > checkPermission above.
> >
> > *snip from PluginAppletSecurityContext.java:658*
> >              PluginDebug.debug("Calling method " + m + " on object " + o
> >                                                + " with " + arguments);
> >
> >                                AccessControlContext acc = callContext != 
> > null ? callContext : getClosedAccessControlContext();
> >                                checkPermission(src, o.getClass(), acc);
> > *snap*
> >
> >
> >>>     at 
> >>> sun.applet.AppletSecurityContextManager.handleMessage(AppletSecurityContextManager.java:31)
> >>>     at 
> >>> sun.applet.PluginStreamHandler.handleMessage(PluginStreamHandler.java:248)
> >>>     at 
> >>> sun.applet.PluginMessageHandlerWorker.run(PluginMessageHandlerWorker.java:34)
> >>>
> >>> Occasionally I also get following error:
> >>> IcedTeaPlugin.cc:4735: Error: parse int
> >>>
> >
> > In IcedTeaPlugin.cc:4735  a lookup to a object seems to have failed in your 
> > case. We need to know what string was used here for the lookup.
> > I dont want to guess but the errors you have experienced might be related.
> >
> > *snip from PluginAppletSecurityContext.java:4735*
> >  case jobject_type:
> >      // Have we referred to this object before?
> >      id = str.ToInteger (&conversionResult);
> >      PLUGIN_CHECK ("parse int", conversionResult);
> >      retval.l = factory->references.ReferenceObject (id);
> >      break;
> > *snap*
> >
> >
> 
> Hi!
> 
> What website do you see this error on?
> 
> As for PluginDebug.debug() ... its messages go to STDERR. However,
> debug() prints only if you have set ICEDTEAPLUGIN_DEBUG=true, and in
> that case, all OUT/ERR is redirected to /tmp/java.stdout and
> /tmp/java.stderr
> 
> Cheers,
> Deepak
> 

Whoops.. should have checked the ML first.

Okay, can you start the browser with the env variable 
ICEDTEAPLUGIN_DEBUG=true , and then send the resulting log 
and /tmp/java.std* files?

Deepak

> 
> > Cheers and have a great day!
> > Xerxes



More information about the distro-pkg-dev mailing list