[cfe-dev] Bug: Unexpected dereference claim on --analyze

Ted Kremenek kremenek at apple.com
Mon Dec 5 22:58:39 PST 2011


On Dec 5, 2011, at 9:27 PM, Jeffrey Yasskin wrote:
>> 
>> Do you think it would be reasonable to still emit a warning here, but
>> categorize it differently in the places where we are less certain that the
>> issue is a null dereference?
> 
> Yes, sorry, I wasn't as clear as I should have been. The warning was
> obnoxious only because it asserted that a possibly-null pointer was
> definitely being dereferenced, when it meant that either a
> possibly-null pointer was being dereferenced OR there was a redundant
> check, and it always hid the location of the possibly-redundant check.
> I would value getting the "redundant check or null dereference"
> warning in my own code: I just want the analyzer to be honest about
> what it's finding and not make overly-certain claims based on dodgy
> assumptions.
> 
> Jeffrey

Makes perfect sense.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20111205/dd0f66f6/attachment.html>


More information about the cfe-dev mailing list