[LLVMbugs] [Bug 19042] New: Calling a +0 ref getting can incorrectly warn about pointer ownership

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=19042

            Bug ID: 19042
           Summary: Calling a +0 ref getting can incorrectly warn about
                    pointer ownership
           Product: clang
           Version: trunk
          Hardware: Macintosh
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: Static Analyzer
          Assignee: kremenek at apple.com
          Reporter: tjw at me.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

Created attachment 12184
  --> http://llvm.org/bugs/attachment.cgi?id=12184&action=edit
example case

In several cases, I'm getting seemingly spurious clang-sa warnings about
releasing non-owned pointers. It seems to happen when a property is accessed
via a getter on the path to releasing the backing ivar:

- (void)dealloc;
{
    [self.object self];
    [_object release];
    [super dealloc];
}

See the attached sample for a reproducible case.

clang version 3.5.0 (trunk 202861)
Target: x86_64-apple-darwin13.1.0
Thread model: posix

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20140304/a5726c5e/attachment.html>