On Mon, Sep 1, 2008 at 3:42 PM, Tim Schwartz tim@sanityinternet.com wrote:
So Austin, have you had a chance to have a discussion with Dan about adding flawfinder to patchwatcher?
On Aug 31, 2008, at 4:12 AM, wine-devel-request@winehq.org wrote:
Send wine-devel mailing list submissions to wine-devel@winehq.org
To subscribe or unsubscribe via the World Wide Web, visit http://www.winehq.org/mailman/listinfo/wine-devel or, via email, send a message with subject or body 'help' to wine-devel-request@winehq.org
You can reach the person managing the list at wine-devel-owner@winehq.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of wine-devel digest..."
Today's Topics:
- Adding Flawfinder to Patchwatcher (Austin English)
Message: 1 Date: Thu, 28 Aug 2008 15:59:20 -0500 From: "Austin English" austinenglish@gmail.com Subject: Adding Flawfinder to Patchwatcher To: "wine-devel@winehq.org" wine-devel@winehq.org Message-ID: b6bb06270808281359o1d1258f9m1af82eddbb763f32@mail.gmail.com Content-Type: text/plain; charset="utf-8"
I had a discussion with Dan about adding Flawfinder to the patchwatcher. Currently, it's got some pretty generic errors, but it seems able to test only patches, so we wouldn't be flooded with old nonbugs (or we could set up a blacklist of safe errors). For reference, I've run it on today's git. I'm attaching the full log, as well as a condensed version of the most common errors (1 per error type). Looks like a lot of chances for buffer overflows..
Thoughts?
-Austin