diff options
| author | Anna Zaks <ganna@apple.com> | 2012-02-11 21:44:39 +0000 |
|---|---|---|
| committer | Anna Zaks <ganna@apple.com> | 2012-02-11 21:44:39 +0000 |
| commit | 0860cd0646ed40f87085df39563f2c5f7f77750b (patch) | |
| tree | 2efece56e02521a5de210e6235ecfb199591845c /test/Analysis/malloc-annotations.c | |
| parent | da04677092c7b08fe7438f82a8636dcc8c6e9683 (diff) | |
[analyzer] Malloc Checker: Report a leak when we are returning freed
memory.
(As per one test case, the existing checker thought that this could
cause a lot of false positives - not sure if that's valid, to be
verified.)
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@150313 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'test/Analysis/malloc-annotations.c')
| -rw-r--r-- | test/Analysis/malloc-annotations.c | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/test/Analysis/malloc-annotations.c b/test/Analysis/malloc-annotations.c index 7890cfc176..98dc2e7269 100644 --- a/test/Analysis/malloc-annotations.c +++ b/test/Analysis/malloc-annotations.c @@ -128,12 +128,10 @@ void af3() { free(p); // no-warning } -// This case would inflict a double-free elsewhere. -// However, this case is considered an analyzer bug since it causes false-positives. int * af4() { int *p = my_malloc(12); my_free(p); - return p; // no-warning + return p; // expected-warning{{Use of dynamically allocated}} } // This case is (possibly) ok, be conservative |