[cfe-dev] Fwd: Does clang analyzer can only report one warning?

J Green greenabc99 at gmail.com
Sun Nov 21 16:21:11 PST 2010


---------- Forwarded message ----------
From: J Green <greenabc99 at gmail.com>
Date: 2010/11/22
Subject: Re: [cfe-dev] Does clang analyzer can only report one warning?
To: Ted Kremenek <kremenek at apple.com>


p.s.
Whether there exists some options to set after command: "clang --analyze "
(i.e. clang --analyze -option_a -option_b? or use scan-build command?)to let
analyzer  show different sources warning messages at the same time?




2010/11/21 J Green <greenabc99 at gmail.com>

Hi, Ted
>     First of all, thank for your quick reply.
>     But I still puzzled for such case: if there exists several same kind of
> bugs, such as uninitialized variables, for example, a and b is two
> uninitialized variables, they do not have any relationship (they are in
> different paths), would they be reported by clang at the same time(give two
> uninitialized warning messages at the same time)?
>
> Thanks again.
>
>
>
> 2010/11/19 Ted Kremenek <kremenek at apple.com>
>
> For some bugs, such as uses of uninitialized variables or a null
>> dereference, the analyzer stops analyzing a given path because the semantics
>> would potentially be meaningless after the point of the bug.  If the second
>> bug is dominated by one of these other fail stop bugs, it won't be reported
>> until the other bug is resolved.  It's a tradeoff; the idea is that people
>> will fix issues, run the analyzer again and uncover new ones, etc.
>>
>> Sent from my iPad
>>
>> On Nov 18, 2010, at 9:18 PM, J Green <greenabc99 at gmail.com> wrote:
>>
>> > Hi, all
>> >
>> >      I just want to use clang static analyzer, the command is : "clang
>> --analyze xxx.c" to check xxx.c's errors. but I can only see one warning
>> message,
>> > for example, one variable is undefined, but there exists another null
>> pointer dereference error after that, why the analyzer can not report null
>> pointer deference warning? Do I miss dothing sth.(e.g. one or more options
>> needed)? or clang analyzer can only report one warning message in one
>> function?
>> >      In other words, How clang analyzer deal with different source
>> errors?  To one kind of errors, just report the first one? or To all kind of
>> errors, just report the first one?
>> >
>> >                          Thanks.
>> >                          J Green
>> > _______________________________________________
>> > cfe-dev mailing list
>> > cfe-dev at cs.uiuc.edu
>> > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20101122/7a832f84/attachment.html>


More information about the cfe-dev mailing list