[cfe-dev] Clang Analysis of several open source projects.

[Ted Kremenek]

On May 12, 2011, at 1:29 PM, Ben Laurie wrote:

> On 12 May 2011 16:08, Ted Kremenek <kremenek at apple.com> wrote:
> On May 12, 2011, at 11:19 AM, John Smith wrote:
> 
>> But my main point wasnt really finding bugs in the projects
>> themselves, but finding & fixing bugs in the analyzer (by decreasing
>> the potential for false positives).
> 
> 
> Thanks John.  That's what I am hopeful for as well.
> 
> To make this exercise the most constructive, we need actual bug reports against the analyzer.  Diagnosing a sea of reports, and complaining that there are too many false positives just really isn't constructive or helpful on its own.
> 
> Typically the bug reports have the following characteristics:
> 
> a) have a concise but precise diagnosis of what the analyzer isn't reasoning about correctly
> 
> b) provides a test case of a preprocessed file that can be used later to reproduce the issue.  (also include the platform/arch you are on when filing the report)
> 
> One thing that could be very usefully added to the output of scan-build is exactly this prepocessed file, which is otherwise painul to prepare...

We can certainly provide this as a scan-build option.  It's probably a bit of perl script hackery, but it could be done.  We wouldn't want to do it all the time, as those preprocessed files can get big.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20110512/c368f949/attachment.html>