[analyzer] -analyzer-output=text in scan-build

Hi,

it is possible, to somehow pass the -analyzer-output=text flag
to scan-build, in order to activate tracing diagnostics
for the command line output? This would be handy, as the scan-build
script eases the static analyzer use for nontrivial build setups
and -analyzer-output=text provides information about traced paths
of implementations defined in headers which are not presented in the
html output.

-Alex

There is no scan-build option that supports it right now. However, it would be trivial to add. $Options{OutputFormat} variable is used to set the value of "-analyzer-output".

Anna.

Thanks for your answer! Is there a reason why this is not
activated in any case by default when the analyzer is invoked?

Apart from that, maybe this option could be integrated into the new
scan-build script? (reviews.llvm.org/D9600)
If there's interest, I could provide a patch to the
script currently hosted on GitHub: https://github.com/rizsotto/Beye.

-Alex

Thanks for your answer! Is there a reason why this is not
activated in any case by default when the analyzer is invoked?

I think it’s about the workflows that are interesting to various users. Plist provides the richest output; this is what is used to view the error reports in Xcode. Scan-build uses the HTML reports. Unfortunately, the cross-file support is still lacking there and there are other problems with the current implementation, such as scalability. The text output is not user friendly; we mainly use it for testing.

Anna.

Interesting, thanks for providing this overview!

-Alex