[Soot-list] How to handle native calls

[Eric Bodden]

Hi Jochen.

Yes that can be done. Spark has a native-method simulation framework.

Look at this method for an example:

soot.jimple.toolkits.pointer.nativemethods.JavaLangSystemNative.java_lang_System_arraycopy(SootMethod,
ReferenceVariable, ReferenceVariable, ReferenceVariable[])

All simulations are instantiated here:
soot.jimple.toolkits.pointer.util.NativeMethodDriver

Eric


On 9 February 2011 13:00, Jochen Huck <jochen.huck at student.kit.edu> wrote:
> Hi,
>
> I use the sideeffect analysis to ensure that two statements have no
> critical data dependencies. If one of these statements calls a native
> method it must be assumed that there might be data dependencies. I just
> wondered wheather it is possible to "inform" soot how to handle special
> native methods (like System.arraycopy()). I would like to say something
> like System.arraycopy(...) affects some points to sets - but the others
> are not affected.
>
> Thanks,
>
> Jochen
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>



-- 
Dr. Eric Bodden, http://bodden.de/
Principal Investigator in Secure Services at CASED
Coordinator of the CASED Advisory Board of Study Affairs
PostDoc at Software Technology Group, Technische Universität Darmstadt
Tel: +49 6151 16-5478    Fax: +49 6151 16-5410
Mailing Address: S2|02 A209, Hochschulstraße 10, 64289 Darmstadt