File: retain-release-cpp-classes.cpp

package info (click to toggle)
llvm-toolchain-11 1%3A11.0.1-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 995,808 kB
  • sloc: cpp: 4,767,656; ansic: 760,916; asm: 477,436; python: 170,940; objc: 69,804; lisp: 29,914; sh: 23,855; f90: 18,173; pascal: 7,551; perl: 7,471; ml: 5,603; awk: 3,489; makefile: 2,573; xml: 915; cs: 573; fortran: 503; javascript: 452
file content (33 lines) | stat: -rw-r--r-- 840 bytes parent folder | download | duplicates (25) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
 
// RUN: %clang_analyze_cc1 -analyzer-checker=core,osx -analyzer-output=text -verify %s

// expected-no-diagnostics

typedef void *CFTypeRef;
typedef struct _CFURLCacheRef *CFURLCacheRef;

CFTypeRef CustomCFRetain(CFTypeRef);
void invalidate(void *);
struct S1 {
  CFTypeRef s;
  CFTypeRef returnFieldAtPlus0() {
    return s;
  }
};
struct S2 {
  S1 *s1;
};
void foo(S1 *s1) {
  invalidate(s1);
  S2 s2;
  s2.s1 = s1;
  CustomCFRetain(s1->returnFieldAtPlus0());

  // Definitely no leak end-of-path note here. The retained pointer
  // is still accessible through s1 and s2.
  ((void) 0); // no-warning

  // FIXME: Ideally we need to warn after this invalidate(). The per-function
  // retain-release contract is violated: the programmer should release
  // the symbol after it was retained, within the same function.
  invalidate(&s2);
}