lebedev.ri abandoned this revision.
lebedev.ri added a comment.
Sad, but ok.
Repository:
rC Clang
https://reviews.llvm.org/D46187
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
NoQ added a comment.
In https://reviews.llvm.org/D46187#1089087, @lebedev.ri wrote:
> > I believe we could also benefit from a method of extracting the analyzer's
> > `clang -cc1` run-line from clang-tidy. This would allow arbitrary debugging
> > over a single analyzer invocation.
>
> I'm not r
alexfh added a comment.
In https://reviews.llvm.org/D46187#1088722, @NoQ wrote:
> It seems that you're using debug checkers of the analyzer to gain some free
> tools for exploring the source code (such as displaying a call graph) for
> free, right?
>
> I believe we could also benefit from a met
lebedev.ri added a comment.
In https://reviews.llvm.org/D46187#1088722, @NoQ wrote:
> It seems that you're using debug checkers of the analyzer to gain some free
> tools for exploring the source code (such as displaying a call graph) for
> free, right?
Yes.
I was interested to dump the callgr
NoQ added a comment.
It seems that you're using debug checkers of the analyzer to gain some free
tools for exploring the source code (such as displaying a call graph) for free,
right?
I believe we could also benefit from a method of extracting the analyzer's
`clang -cc1` run-line from clang-ti
alexfh added a comment.
What's the use case for debug CSA checkers in clang-tidy?
Repository:
rC Clang
https://reviews.llvm.org/D46187
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-comm
lebedev.ri created this revision.
lebedev.ri added reviewers: dcoughlin, alexfh, aaron.ballman, george.karpenkov,
NoQ.
Herald added subscribers: a.sidorin, szepet, xazax.hun.
I would like to be able to trigger these debug checkers from clang-tidy, as a
follow-up patch for https://reviews.llvm.or
