Wireshark mailing list archives
Re: strlen() and NULL pointer checks
From: Jeff Morriss <jeff.morriss.ws () gmail com>
Date: Tue, 17 May 2011 12:37:44 -0400
Jeff Morriss wrote:
Jakub Zawadzki wrote:- I had the same issue with another project, and we created macro: #define __(x) ((x) ? (x) : "(null)")and use it when passing possible-null-strings. It's still PITA but IMHO it looks a little better than doing it by hand.I don't mind doing it by hand (and in some cases I prefer NOT having another layer of abstraction), but then we still need to have a way to (regularly) test for it.
Oh, and I figured fuzz testing on the Solaris buildbot would not be a good solution because only people with access to Solaris boxes would be able to reproduce the crash...
___________________________________________________________________________ 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:
- strlen() and NULL pointer checks Jeff Morriss (May 16)
- Re: strlen() and NULL pointer checks Chris Maynard (May 16)
- Re: strlen() and NULL pointer checks Gerald Combs (May 16)
- Re: strlen() and NULL pointer checks Jeff Morriss (May 16)
- Re: strlen() and NULL pointer checks Jakub Zawadzki (May 16)
- Re: strlen() and NULL pointer checks Jeff Morriss (May 16)
- Re: strlen() and NULL pointer checks Guy Harris (May 16)
- Re: strlen() and NULL pointer checks Jeff Morriss (May 17)
- Re: strlen() and NULL pointer checks Jeff Morriss (May 16)
- Re: strlen() and NULL pointer checks Chris Maynard (May 16)