Wireshark mailing list archives
Re: clang analysis
From: Stephen Fisher <steve () stephen-fisher com>
Date: Sun, 9 May 2010 16:08:12 -0600
On Sun, May 09, 2010 at 11:56:50PM +0300, Kaul wrote:
Oy Vey! I've just built clang from SVN and now it finds 3354 bugs. Regretfully, its report is not file based - it just shows them one after another, not sorted by file.
I'm not even sure how to open a bug on so many files, and it would be quite difficult go through each file and report the bug. The report ( 6 HTMLs, uncompressed) is 1.8MB - should I perhaps zip and file a single bug? I'm almost done with the fixes to packet-ssl.c, but there are so many others...
Sorry, I wasn't clear on what I meant. If you could open a bug just saying that you're running clang version <whatever> and it found thousands of bugs, that's enough :). It's just a hint to others to run clang on their own and see what can/should be fixed. -- Steve ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- clang analysis Kaul (May 01)
- Wireshark can not open file David (May 01)
- Re: Wireshark can not open file Stephen Fisher (May 02)
- Re: clang analysis Stephen Fisher (May 04)
- Re: clang analysis Kaul (May 09)
- Re: clang analysis Stephen Fisher (May 09)
- Re: clang analysis Bill Meier (May 11)
- Re: clang analysis Kaul (May 09)
- Wireshark can not open file David (May 01)