From e8d556742690e1a9cd864dfe035dc50581d97717 Mon Sep 17 00:00:00 2001
From: Jordan Rose <jordan_rose@apple.com>
Date: Mon, 2 Jul 2012 21:41:56 +0000
Subject: [PATCH] [analyzer] If 'super' is known to be nil, we can still mark
 its range.

llvm-svn: 159596
---
 clang/lib/StaticAnalyzer/Checkers/CallAndMessageChecker.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/clang/lib/StaticAnalyzer/Checkers/CallAndMessageChecker.cpp b/clang/lib/StaticAnalyzer/Checkers/CallAndMessageChecker.cpp
index 2f95709e03b2..69b331c16cc9 100644
--- a/clang/lib/StaticAnalyzer/Checkers/CallAndMessageChecker.cpp
+++ b/clang/lib/StaticAnalyzer/Checkers/CallAndMessageChecker.cpp
@@ -310,9 +310,9 @@ void CallAndMessageChecker::emitNilReceiverBug(CheckerContext &C,
   os << "' that will be garbage";
 
   BugReport *report = new BugReport(*BT_msg_ret, os.str(), N);
+  report->addRange(msg.getReceiverSourceRange());
   // FIXME: This won't track "self" in messages to super.
   if (const Expr *receiver = msg.getInstanceReceiverExpr()) {
-    report->addRange(receiver->getSourceRange());
     report->addVisitor(bugreporter::getTrackNullOrUndefValueVisitor(N,
                                                                     receiver,
                                                                     report));
-- 
GitLab