[cfe-dev] Analyzing DragonFly BSD

Török Edwin edwintorok at gmail.com
Fri Aug 22 00:07:34 PDT 2008

On 2008-08-21 23:44, Ted Kremenek wrote:
> On Aug 21, 2008, at 11:31 AM, Sascha Wildner wrote:
>> * Interestingly, the "null dereference" count went down from 308 in 
>> http://yoyodyne.ath.cx/ccc-analyze/buildkernel/2008-08-10-1/ to 119 in 
>> http://yoyodyne.ath.cx/ccc-analyze/buildkernel/2008-08-21-2/ (we fixed a 
>> couple but not that many). Some of them were valid bugs, according to 
>> one guy from our team.
> Hi Sascha,
> Another useful thing is if people want to provide us preprocessed
> sources that the analyzer *correctly* identified bugs in.  This would
> allow us to incrementally add valid bug reports to our test suite.
> This is something that we can actually add to scan-build.  For every
> source file that the analyzer flags an error, we can also
> automatically generate preprocessed .i/.mi files.  Users can then
> submit these to us if they wish for either the case that the bug is a
> false positive or that it's valid.  Building up a test suite of
> validated bugs would be invaluable.
> Ted

I could send you some examples where clang didn't identify a bug
(another checkers found the bug, or it was discovered during a manual
code review).
Would that be useful?

Best regards,

More information about the cfe-dev mailing list