[cfe-dev] scan-build in python

[Laszlo Nagy]

thanks Jordan for the reply.

> This is the right list for analyzer questions. Ted Kremenek, Anna Zaks, and I are the primary maintainers.
> What in particular is broken in ccc-analyze / scan-build?

small thing i found, when `ccc-analyzer` processes the arguments, take
'-m.*' and put into the CompileOpts. then a few lines bellow there is
a CompilerLinkerOptionMap lookup which has 5 parameters starting with
'-m'. which implies they never gonna end up in CompileOpts _and_
LinkOpts.

also wondered many times where are these flags coming from? like
'-arch'? clang/gcc does not have it. (found a few others which are
also not found in clang/gcc.) which compiler tries the 'ccc-analyze'
simulate?

> Also, being able to run the analyzer against a compilation database seems like a good feature. I think the auxiliary "clang-check" executable can already do this with its -analyze option, though I haven't tried it, but it doesn't allow for much customization of the output like scan-build does. Still, it could give you a place to start.

was not aware about 'clang-check' existence. although the usage of it
i find a little bit ugly. :) guess it's the tooling library which make
it like this. will look at it to see how it works. thanks.

regards,
Laszlo