Re: Suggestions on writing a source code analyzer.

Jeff Kenton <jeffrey.kenton@comcast.net>
8 Nov 2005 23:35:34 -0500

          From comp.compilers
Related articles
Suggestions on writing a source code analyzer. imanpreet@gmail.com (Minti) (2005-11-04)
Re: Suggestions on writing a source code analyzer. bill@qswtools.com (Bill Cox) (2005-11-08)
Re: Suggestions on writing a source code analyzer. jeffrey.kenton@comcast.net (Jeff Kenton) (2005-11-08)
Re: Suggestions on writing a source code analyzer. mackay_d@hotmail.com (Don Mackay) (2005-11-12)
| List of all articles for this month |
From: Jeff Kenton <jeffrey.kenton@comcast.net>
Newsgroups: comp.compilers
Date: 8 Nov 2005 23:35:34 -0500
Organization: Compilers Central
References: 05-11-041
Keywords: analysis
Posted-Date: 08 Nov 2005 23:35:34 EST

Minti wrote:
> Could anyone provide any pointers regarding source code
> analysis?


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.


jeff


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.