|Suggestions on writing a source code analyzer. email@example.com (Minti) (2005-11-04)|
|Re: Suggestions on writing a source code analyzer. firstname.lastname@example.org (Bill Cox) (2005-11-08)|
|Re: Suggestions on writing a source code analyzer. email@example.com (Jeff Kenton) (2005-11-08)|
|Re: Suggestions on writing a source code analyzer. firstname.lastname@example.org (Don Mackay) (2005-11-12)|
|From:||Jeff Kenton <email@example.com>|
|Date:||8 Nov 2005 23:35:34 -0500|
|Posted-Date:||08 Nov 2005 23:35:34 EST|
> Could anyone provide any pointers regarding source code
Analysis for what purpose? To detect bugs? To find security holes? To analyze
code complexity? Two companies that come to mind in the bugs and security area
are Ounce Labs and Klokwork.
If you're doing your own, you will definitely need a parser for the
language(s) in question for any but the most trivial analysis. After that,
your analysis phase depends on the answers to the questions above. You may
need to track control flow and value propagation, or other things, depending
on your needs.
Return to the
Search the comp.compilers archives again.