Re: [Wireshark-dev] [Wireshark-commits] rev 37187: /trunk/ /trunk/: dumpcap.c

2011-05-16 Thread Maynard, Chris
From: wireshark-dev-boun...@wireshark.org [wireshark-dev-boun...@wireshark.org] On Behalf Of Michael Tüxen [michael.tue...@micmac.franken.de] Sent: Monday, May 16, 2011 4:34 PM To: wireshark-dev@wireshark.org Subject: Re: [Wireshark-dev] [Wireshark-commits]

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-7-x64

2011-05-16 Thread buildbot-no-reply
The Buildbot has detected a new failure of Windows-7-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/1862 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason:

Re: [Wireshark-dev] [Wireshark-commits] rev 37187: /trunk/ /trunk/: dumpcap.c

2011-05-16 Thread Michael Tüxen
On May 16, 2011, at 9:56 PM, cmayn...@wireshark.org wrote: > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=37187 > > User: cmaynard > Date: 2011/05/16 12:56 PM > > Log: > #include when compiling under Windows with DEBUG_DUMPCAP defined. Ahh, thanks a lot! Best regards Michae

[Wireshark-dev] Wireshark 1.6.0rc1 is now available

2011-05-16 Thread Gerald Combs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 1.6.0rc1. This is the first release candidate of the upcoming 1.6 (stable) branch. What is Wireshark? Wireshark is the world's most popular network protocol analyzer. It is used for troubleshooting

Re: [Wireshark-dev] strlen() and NULL pointer checks

2011-05-16 Thread Guy Harris
On May 16, 2011, at 2:53 PM, Jeff Morriss wrote: > But it is encouraging as they indicate that Solaris is the only "significant" > printf that is "good enough" except for this NULL pointer stuff. Well, > except for those poor sods running "insignificant" printfs. To be fair, what Owen said wa

Re: [Wireshark-dev] strlen() and NULL pointer checks

2011-05-16 Thread Jeff Morriss
Jakub Zawadzki wrote: On Mon, May 16, 2011 at 04:18:40PM -0400, Jeff Morriss wrote: Every once in a while, I do some fuzz testing on a Solaris/SPARC system. When I first did it I was primarily worried about getting bus errors (due to casts increasing alignment requirements), but usually what

Re: [Wireshark-dev] strlen() and NULL pointer checks

2011-05-16 Thread Jeff Morriss
Chris Maynard wrote: Jeff Morriss writes: Is there a better way? Or better yet, a proper solution? Not claiming this is better or proper, just another alternative: epan/strutil.c: #include size_t ws_strlen(const char *s) { if (s == NULL) return 0; return strlen(s); } Bu

Re: [Wireshark-dev] strlen() and NULL pointer checks

2011-05-16 Thread Jakub Zawadzki
On Mon, May 16, 2011 at 04:18:40PM -0400, Jeff Morriss wrote: > Every once in a while, I do some fuzz testing on a Solaris/SPARC system. > When I first did it I was primarily worried about getting bus errors > (due to casts increasing alignment requirements), but usually what I > find is anoth

Re: [Wireshark-dev] strlen() and NULL pointer checks

2011-05-16 Thread Gerald Combs
On 5/16/11 1:47 PM, Chris Maynard wrote: > Jeff Morriss writes: > >> Is there a better way? Or better yet, a proper solution? > > Not claiming this is better or proper, just another alternative: > > epan/strutil.c: > > #include > size_t ws_strlen(const char *s) > { > if (s == NULL) >

Re: [Wireshark-dev] strlen() and NULL pointer checks

2011-05-16 Thread Chris Maynard
Jeff Morriss writes: > Is there a better way? Or better yet, a proper solution? Not claiming this is better or proper, just another alternative: epan/strutil.c: #include size_t ws_strlen(const char *s) { if (s == NULL) return 0; return strlen(s); }

[Wireshark-dev] strlen() and NULL pointer checks

2011-05-16 Thread Jeff Morriss
Hi folks, Every once in a while, I do some fuzz testing on a Solaris/SPARC system. When I first did it I was primarily worried about getting bus errors (due to casts increasing alignment requirements), but usually what I find is another case of what I fixed in r37181. (Fortunately, I have n

Re: [Wireshark-dev] [Wireshark-commits] rev 37016: /trunk/gtk/ /trunk/gtk/: main_welcome.c

2011-05-16 Thread Stephen Fisher
This is a great idea. What is/where is "capture help" that it refers to? It would be great if it could be a clickable link to take the user there. On Sun, May 08, 2011 at 10:59:24AM +, rbal...@wireshark.org wrote: > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=37016 >

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-XP-x86

2011-05-16 Thread buildbot-no-reply
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/2975 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason

Re: [Wireshark-dev] Solaris buildbot's GTK?

2011-05-16 Thread Gerald Combs
On 5/16/11 6:33 AM, Jeff Morriss wrote: > Hi Gerald, > > The Solaris buildbot can't find its GTK any more: > >> checking for GTK+ - version >= 2.4.0... no >> *** Could not run GTK+ test program, checking why... >> *** The test program failed to compile or link. See the file >> config.log for the

[Wireshark-dev] buildbot failure in Wireshark (development) on Visual-Studio-Code-Analysis

2011-05-16 Thread buildbot-no-reply
The Buildbot has detected a new failure of Visual-Studio-Code-Analysis on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Visual-Studio-Code-Analysis/builds/769 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: vs

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-7-x64

2011-05-16 Thread buildbot-no-reply
The Buildbot has detected a new failure of Windows-7-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/1855 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason:

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-XP-x86

2011-05-16 Thread buildbot-no-reply
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/2969 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason

[Wireshark-dev] Solaris buildbot's GTK?

2011-05-16 Thread Jeff Morriss
Hi Gerald, The Solaris buildbot can't find its GTK any more: checking for GTK+ - version >= 2.4.0... no *** Could not run GTK+ test program, checking why... *** The test program failed to compile or link. See the file config.log for the *** exact error that occured. This usually means GTK+ is i