Tom Tromey wrote:
That said, if I were doing static analysis of Java, I would not try to
use gcj. It is simpler to either put code into an existing compiler
(Eclipse or the JDK's), or to use one of the existing analysis
frameworks (FindBugs, or roll your own with ASM).
I can't recommend soot[1] highly enough; it's actively developed, has a
great user community, is easy to use, and comes with most of the
functionality you'd need to build on for sophisticated analyses already
baked in. I've used it to design several analyses and build a Java
analysis framework based on logic programming.[2]
Some former colleagues have had some success with Wala[3]; it is pretty
tightly coupled to eclipse, though, which might make it difficult to use
in a batch environment.
best,
wb
[1] http://www.sable.mcgill.ca/soot
[2] for more information, see the publication list here:
http://pages.cs.wisc.edu/~willb/
[3] http://wala.sourceforge.net/wiki/index.php/Main_Page
--
William C. Benton <[email protected]>
Senior Software Engineer, Red Hat MRG
_______________________________________________
dev-static-analysis mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-static-analysis
