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

[Artem Dergachev via Phabricator via cfe-commits]

NoQ added a comment.

In https://reviews.llvm.org/D40809#955929, @dcoughlin wrote:

> As it stands, this is a debugging tool not a way to communicate error paths to end users. (I think that, too, would be very helpful but I'd like to see this as a debugging aid first.) The workflow for debugging would be more like viewing the exploded graph than (say) emitting html diagnostics.
>
> My point is this: this is valuable as a debugging tool, we should get it committed as such. We can work on making it user facing separately.


Per-report dumps are still much more useful for a debugging tool than whole-graph dumps. I guess such tool would be used on live code, not on reduced examples, and in this case there would be a *lot* of noise we'd want to avoid.


https://reviews.llvm.org/D40809