Re: How to deal with implicit call in Spark?

[Feng QIAN <fqian@sable.mcgill.ca>]

It is not a fault of the Spark. The side effect of native methods are
simulated in soot/jimple/toolkits/pointer/nativemethods, for example,
AccessController.doPrivileged is simulated in
JavaSecurityAccessControllerNative.java. The return variable of
doPrivileged is assigned a least object:
NativeHelper.assignObjectTo(returnVar, Environment.v().getLeastObject());

I am not sure if this addresses your concern?

Cheers,
-- Feng

On Wed, 21 May 2003, CHEN FU wrote:

>
> I'm using spark to do points to analysis on a whole program based on
> jdk1.3
>
> Object AccessController.doPrivileged(PrivilegedExceptionAction action)
>
> The above is a native method which calls
>
> Object PrivilegedExceptionAction.run()
>
> implicitly. The problem here is that some object in method action.run()
> may flow back to the caller of the AccessController.doPrivileged via
> method returns. It seems that spark does not process this dataflow by
> default.
>
>