[PATCH] D40809: [WIP] [analyzer] Dump counterexample traces as C programs

[Artem Dergachev via Phabricator via cfe-commits]

NoQ added a comment.

This looks great for understanding what exactly is going on in a large real-world report.

If you want to turn this into a form of user-facing analyzer output variant, you may want to implement it as a `PathDiagnosticConsumer` rather than a visitor. If we only want a neat debugging mechanism, then you might want to stick it directly into `BugReporter::emitReport()` or maybe `BugReporter::FlushReport()` (not sure how both of these interact with report deduplication).


https://reviews.llvm.org/D40809