<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On May 12, 2011, at 1:29 PM, Ben Laurie wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">On 12 May 2011 16:08, Ted Kremenek<span class="Apple-converted-space"> </span><span dir="ltr"><<a href="mailto:kremenek@apple.com">kremenek@apple.com</a>></span><span class="Apple-converted-space"> </span>wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; "><div style="word-wrap: break-word; "><div class="im"><div><div>On May 12, 2011, at 11:19 AM, John Smith wrote:</div><br><blockquote type="cite"><span style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; font-size: medium; ">But my main point wasnt really finding bugs in the projects<br>themselves, but finding & fixing bugs in the analyzer (by decreasing<br>the potential for false positives).</span></blockquote></div><div><br></div></div><div>Thanks John. That's what I am hopeful for as well.</div><div><br></div><div>To make this exercise the most constructive, we need actual bug reports against the analyzer. Diagnosing a sea of reports, and complaining that there are too many false positives just really isn't constructive or helpful on its own.</div><div><br></div><div>Typically the bug reports have the following characteristics:</div><div><br></div><div>a) have a concise but precise diagnosis of what the analyzer isn't reasoning about correctly</div><div><br></div><div>b) provides a test case of a preprocessed file that can be used later to reproduce the issue. (also include the platform/arch you are on when filing the report)</div></div></blockquote><div><br></div><div>One thing that could be very usefully added to the output of scan-build is exactly this prepocessed file, which is otherwise painul to prepare...</div></span></blockquote></div><br><div>We can certainly provide this as a scan-build option. It's probably a bit of perl script hackery, but it could be done. We wouldn't want to do it all the time, as those preprocessed files can get big.</div></body></html>