File: retain-release-cpp-classes.cpp

package info (click to toggle)
llvm-toolchain-14 1%3A14.0.6-20
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 1,496,436 kB
  • sloc: cpp: 5,593,990; ansic: 986,873; asm: 585,869; python: 184,223; objc: 72,530; lisp: 31,119; f90: 27,793; javascript: 9,780; pascal: 9,762; sh: 9,482; perl: 7,468; ml: 5,432; awk: 3,523; makefile: 2,547; xml: 953; cs: 573; fortran: 567
file content (33 lines) | stat: -rw-r--r-- 840 bytes parent folder | download | duplicates (23) 
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);
}