[cfe-dev] Diagnostic won't emit
Andrzej Warzynski via cfe-dev
cfe-dev at lists.llvm.org
Fri Oct 9 12:18:17 PDT 2020
It's a bit tricky to help without seeing the code :) Are you using any
specific/custom diagnostic consumer? Is your properly DiagnosticBuilder
destroyed? AFAIK, that's when the message is printed.
Here's a bit more up-to-date example:
And a test that verifies that the diagnostic is indeed printed:
Happy to help if that example doesn't work for you! Hopefully it will
help debugging your own code :)
On 09/10/2020 16:26, Billy O'Mahony via cfe-dev wrote:
> hopefully a straightforward issue.
> I have written a standalone cfe tool to catch some project-specific bugs
> in a code base.
> I am now replacing my cout << "ERROR..." messages with
> clang::Diagnostics by following this example:
> However I don't see anything being printed when I run it (except my own
> cout << "error.." messages)..
> I've seen the mcabbe example generate diagnostics on a
> youtube presentation and both it and my app use
> clang::Tool. mccabbe uses ast_matcher::MatchFinder whereas I use
> several classes derived from RecursiveASTVisitor. Presumably MatchFinder
> sets up a DiagnosticsConsumer that finally emits the diagnostics??
> But I couldn't really find out how to set up a DiagnosticsConsumer - if
> that is indeed what I need to do.
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
More information about the cfe-dev