I think "actionable" is the keyword here. Dumping the error messages straight from the tool into a bug report does not tell the recipient (a) how many false po

I think "actionable" is the keyword here. Dumping the error messages straight from the tool into a bug report does not tell the recipient (a) how many false positives there are - either code paths that don't occur in the wild or undefined behaviours that actually yield the same result in all sensible implementations (as the a+b-c versus a+(b-c) case), or what possible/likely consequences of such implementation-dependent behaviour would be. (b) how he/she can reproduce the bug to see if it disappeared (hence the PHP guy's request about the exact test cases these errors occur in) It's also not quite helpful if people cannot run the debugging tool themselves. This is pretty independent of whether the tool uses static analysis, or runtime debugging, or a mixture of both.