test/Analysis/stackaddrleak.c

   1 // RUN: %clang_cc1 -analyze -analyzer-check-objc-mem -analyzer-checker=core.StackAddrLeak -analyzer-store region -verify %s
   2
   3 char const *p;
   4
   5 void f0() {
   6   char const str[] = "This will change";
   7   p = str; // expected-warning{{Address of stack memory associated with local variable 'str' is still referred to by the global variable 'p' upon returning to the caller.  This will be a dangling reference}}
   8 }
   9
  10 void f1() {
  11   char const str[] = "This will change";
  12   p = str;
  13   p = 0; // no-warning
  14 }
  15
  16 void f2() {
  17   p = (const char *) __builtin_alloca(12);  // expected-warning{{Address of stack memory allocated by call to alloca() on line 17 is still referred to by the global variable 'p' upon returning to the caller.  This will be a dangling reference}}
  18 }
  19
  20 // PR 7383 - previosly the stack address checker would crash on this example
  21 //  because it would attempt to do a direct load from 'pr7383_list'.
  22 static int pr7383(__const char *__)
  23 {
  24   return 0;
  25 }
  26 extern __const char *__const pr7383_list[];
  27
  28 // Test that we catch multiple returns via globals when analyzing a function.
  29 void test_multi_return() {
  30   static int *a, *b;
  31   int x;
  32   a = &x;
  33   b = &x; // expected-warning{{Address of stack memory associated with local variable 'x' is still referred to by the global variable 'a' upon returning}} expected-warning{{Address of stack memory associated with local variable 'x' is still referred to by the global variable 'b' upon returning}}
  34 }