Index: include/clang/Driver/CC1Options.td =================================================================== --- include/clang/Driver/CC1Options.td +++ include/clang/Driver/CC1Options.td @@ -70,7 +70,7 @@ def analyzer_display_progress : Flag<["-"], "analyzer-display-progress">, HelpText<"Emit verbose output about the analyzer's progress">; def analyze_function : Separate<["-"], "analyze-function">, - HelpText<"Run analysis on specific function">; + HelpText<"Run analysis on specific function (for C++ include parameters in name)">; def analyze_function_EQ : Joined<["-"], "analyze-function=">, Alias; def analyzer_eagerly_assume : Flag<["-"], "analyzer-eagerly-assume">, HelpText<"Eagerly assume the truth/falseness of some symbolic constraints">; Index: www/analyzer/checker_dev_manual.html =================================================================== --- www/analyzer/checker_dev_manual.html +++ www/analyzer/checker_dev_manual.html @@ -575,8 +575,8 @@ processing a large file use the -analyzer-display-progress option.

-

You can analyze a particular function within the file, which is often useful -because the problem is always in a certain function:

+

To selectively analyze only the given function, use the +-analyze-function option:

     $ clang -cc1 -analyze -analyzer-checker=core test.c -analyzer-display-progress
     ANALYZE (Syntax): test.c foo
@@ -588,6 +588,16 @@
     ANALYZE (Path,  Inline_Regular): test.c foo
 
+Note: a fully qualified function name has to be used when selecting +C++ functions and methods, Objective-C methods and blocks, e.g.: + +
+    $ clang -cc1 -analyze -analyzer-checker=core test.cc -analyze-function=foo(int)
+
+ +The fully qualified name can be found from the +-analyzer-display-progress output. +

The bug reporter mechanism removes path diagnostics inside intermediate function calls that have returned by the time the bug was found and contain no interesting pieces. Usually it is up to the checkers to produce more