aboutsummaryrefslogtreecommitdiff
path: root/test/Analysis/malloc.cpp
diff options
context:
space:
mode:
authorJordan Rose <jordan_rose@apple.com>2012-11-15 19:11:43 +0000
committerJordan Rose <jordan_rose@apple.com>2012-11-15 19:11:43 +0000
commit63bc186d6ac0b44ba4ec6fccb5f471b05c79b666 (patch)
tree9002c9a95686003fd8a0ed2875fe5b114d4c4bde /test/Analysis/malloc.cpp
parentf34a5791c5c9df0348714e275adb09b8cf858460 (diff)
[analyzer] Report leaks at the closing brace of a function body.
This fixes a few cases where we'd emit path notes like this: +---+ 1| v p = malloc(len); ^ |2 +---+ In general this should make path notes more consistent and more correct, especially in cases where the leak happens on the false branch of an if that jumps directly to the end of the function. There are a couple places where the leak is reported farther away from the cause; these are usually cases where there are several levels of nested braces before the end of the function. This still matches our current behavior for when there /is/ a statement after all the braces, though. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@168070 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'test/Analysis/malloc.cpp')
-rw-r--r--test/Analysis/malloc.cpp4
1 files changed, 2 insertions, 2 deletions
diff --git a/test/Analysis/malloc.cpp b/test/Analysis/malloc.cpp
index 220d74625b..58b94ea774 100644
--- a/test/Analysis/malloc.cpp
+++ b/test/Analysis/malloc.cpp
@@ -8,8 +8,8 @@ void *calloc(size_t nmemb, size_t size);
void checkThatMallocCheckerIsRunning() {
- malloc(4); // expected-warning{{leak}}
-}
+ malloc(4);
+} // expected-warning{{leak}}
// Test for radar://11110132.
struct Foo {