[Soot-list] running static analysis..

Quentin Sabah quentin.sabah at inria.fr
Thu Jan 3 04:57:33 EST 2013


Hi Zeinab, 

I think what you describe is the main use-case of Soot. Default behavior of Soot's "main loop" is to output final results to files, but you can skip that part and simply harvest Soot's results programmaticaly. 

You can embed several static analyses into a much larger project of yours. However I feel Soot's current design encourages you to embed your analysis into the framework (as phases and packs) more than the other way around: http://www.bodden.de/2008/11/26/soot-packs/

On Jan 2, 2013, at 8:07 PM, Zeinab Lashkaripour wrote:

> Hi,
> I have a question,
> I want to create an automatic tool that part of it uses Soot (for its static analysis), is there a way to run the analysis so that after giving an output for example XML I would be able to use it?
> I mean some way except the plugin of eclipse, because in that way the tool won't be automatic.
>  
> Best Regards,
> 
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list

-- 
Quentin Sabah, CIFRE Ph.D. student
Grenoble University
INRIA-SARDES                   | STMicroelectronics/AST
Montbonnot, France             | Grenoble, France
mailto:quentin.sabah at inria.fr  | mailto:quentin.sabah at st.com
phone: +33 476 61 52 42        | phone: +33 476 58 44 14



More information about the Soot-list mailing list