[Soot-list] Soot class loading

Norbert Sándor developer at erinors.com
Wed Aug 14 10:01:37 EDT 2013


Hello,

Thanks for your quick answer, I will look at Scene.v().forceResolve.

I found another solution which seems to work in my case: 
SourceLocator.v().additionalClassLoader(javassistClassloader);

Best regards:
Norbert Sándor

On 2013.08.14. 15:32, Marc-André Laverdière wrote:
> Hi Norbert,
>
> Generating classes is possible. Bernhard and I have written some code
> for JEE that does that. We do it in the wjpp phase, and the trick is to
> use Scene.v().forceResolve.
>
> Flowdroid also generates some stubs, and they do it before running
> analyses (they don't use soot main, so I don't know in which 'phase'
> that would fit in)
>
> When it comes to classloaders, I have observed a need along those lines.
> Soot has all the classes in a single scope in Scene. This is a problem
> for JEE applications because of the hierarchical classloading scheme.
>
> Implementing this is going to be a lot of work. And it is critical to
> preserve backwards-compatibility, which makes things even trickier. That
> is probably why nobody did it yet :)
>
> As for when the loading happens...
> There is going to be a first loading phase at the start. Then if any
> transformer request a class that isn't there using forceResolve. Then in
> Spark. That should be it.
>



More information about the Soot-list mailing list