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

2011-05-17 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/796 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: vs

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-PowerPC

2011-05-17 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.5-PowerPC on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-PowerPC/builds/2763 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-ppc Build Reas

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-x86

2011-05-17 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/3203 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Bui

[Wireshark-dev] buildbot failure in Wireshark 1.2 on Windows-XP-x86

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

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.6-x64

2011-05-17 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.6-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.6-x64/builds/2754 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.6-x64 Build Reason: Bui

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

2011-05-17 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/1876 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-17 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/2988 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason

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

2011-05-17 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/1872 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason:

[Wireshark-dev] wireshark dev e-mail list

2011-05-17 Thread Brian Oleksa
Is the wireshark dev e-mail list down..?? Just wondering. Thanks, Brian ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/opt

Re: [Wireshark-dev] [Wireshark-commits] rev 37201: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-ncp2222.inc

2011-05-17 Thread Jeff Morriss
Jeff Morriss wrote: Maynard, Chris wrote: -Original Message- From: wireshark-commits-boun...@wireshark.org [mailto:wireshark- commits-boun...@wireshark.org] On Behalf Of morr...@wireshark.org Sent: Tuesday, May 17, 2011 12:08 PM To: wireshark-comm...@wireshark.org Subject: [Wireshark-com

Re: [Wireshark-dev] [Wireshark-commits] rev 37201: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-ncp2222.inc

2011-05-17 Thread Guy Harris
On May 17, 2011, at 9:35 AM, Maynard, Chris wrote: > What about changing match_strval() to behave like val_to_str() does (i.e., > make IT handle the NULL case), That would require code that uses match_strval() to check whether a given numeric value has a match in the value_string table or not

Re: [Wireshark-dev] dissecting bits versus bytes

2011-05-17 Thread Jakub Zawadzki
On Tue, May 17, 2011 at 10:28:23AM -0400, Brian Oleksa wrote: > I am dissecting bits not bytes. I am running into some problems. > ... > Any help with this is greatly appreciated. You can try using proto_tree_add_bits_item(), hth. __

Re: [Wireshark-dev] [Wireshark-commits] rev 37201: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-ncp2222.inc

2011-05-17 Thread Jeff Morriss
Maynard, Chris wrote: -Original Message- From: wireshark-commits-boun...@wireshark.org [mailto:wireshark- commits-boun...@wireshark.org] On Behalf Of morr...@wireshark.org Sent: Tuesday, May 17, 2011 12:08 PM To: wireshark-comm...@wireshark.org Subject: [Wireshark-commits] rev 37201: /tru

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

2011-05-17 Thread Jeff Morriss
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 i

Re: [Wireshark-dev] [Wireshark-commits] rev 37201: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-ncp2222.inc

2011-05-17 Thread Maynard, Chris
> -Original Message- > From: wireshark-commits-boun...@wireshark.org [mailto:wireshark- > commits-boun...@wireshark.org] On Behalf Of morr...@wireshark.org > Sent: Tuesday, May 17, 2011 12:08 PM > To: wireshark-comm...@wireshark.org > Subject: [Wireshark-commits] rev 37201: /trunk/epan/diss

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

2011-05-17 Thread Stephen Fisher
On Tue, May 17, 2011 at 05:13:35PM +0200, Balint Reczey wrote: > It is expected to be one inch below the text. :-) I wanted to make it > as clear as possible, but obviously I failed. How could it be made > clearer? It's further down on my screen :). Just saying "See the capture help below" wo

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

2011-05-17 Thread Balint Reczey
It is expected to be one inch below the text. :-) I wanted to make it as clear as possible, but obviously I failed. How could it be made clearer? I also updated documentation in docbook ant the wiki with Debian related help. Cheers, Balint On 05/16/2011 08:58 PM, Stephen Fisher wrote: This is

[Wireshark-dev] climbing trees

2011-05-17 Thread Ed Beroset
(I posted this email twelve hours ago, but it hasn't shown up, so I'm resending. Sorry if it's a duplicate.) I've updated the patch for bug 5531 per comments from Jeff Morriss (thanks, Jeff!) but he brought up a comment I don't know how to address, so I thought I'd ask here. The comment is on

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

2011-05-17 Thread buildbot-no-reply
The Buildbot has detected a new failure of Clang-Code-Analysis on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Clang-Code-Analysis/builds/120 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: clang-code-analysis