blob: ada0cc10690575ddb8b379a8c7438d4b651b9fdb [file] [log] [blame]
Argyrios Kyrtzidisc4d2c902011-02-28 19:49:42 +00001// RUN: %clang_cc1 -analyze -analyzer-checker=core -analyzer-store region -verify %s
Zhongxing Xu1622a542010-06-08 10:00:00 +00002
3char const *p;
4
5void f0() {
6 char const str[] = "This will change";
Ted Kremeneka8166152010-06-17 04:21:37 +00007 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}}
Zhongxing Xu1622a542010-06-08 10:00:00 +00008}
9
10void f1() {
11 char const str[] = "This will change";
12 p = str;
13 p = 0; // no-warning
14}
Zhongxing Xu2c464582010-06-09 05:50:38 +000015
16void f2() {
Ted Kremeneka8166152010-06-17 04:21:37 +000017 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}}
Zhongxing Xu2c464582010-06-09 05:50:38 +000018}
Ted Kremenek551bd1f2010-06-17 00:24:44 +000019
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'.
22static int pr7383(__const char *__)
23{
24 return 0;
25}
26extern __const char *__const pr7383_list[];
Ted Kremeneka8166152010-06-17 04:21:37 +000027
28// Test that we catch multiple returns via globals when analyzing a function.
29void 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}