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

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

Re: [Wireshark-dev] [Wireshark-commits] rev 36462: / /trunk/tools/: Makefile.am list_protos_in_cap.sh

2011-04-04 Thread Jeff Morriss
On 04/04/2011 06:09 PM, Stephen Fisher wrote: On Mon, Apr 04, 2011 at 07:10:39PM +, morr...@wireshark.org wrote: A little script to extract the protocols used in given capture files. (Just so I don't have to remember how to do it again.) Great idea. It says at the top the default di

Re: [Wireshark-dev] [Wireshark-commits] rev 36462: / /trunk/tools/: Makefile.am list_protos_in_cap.sh

2011-04-04 Thread Stephen Fisher
On Mon, Apr 04, 2011 at 07:10:39PM +, morr...@wireshark.org wrote: > A little script to extract the protocols used in given capture files. > > (Just so I don't have to remember how to do it again.) Great idea. It says at the top the default directory that contains binaries (BIN_DIR) is

[Wireshark-dev] Q re a possible bug for someone familiar with packet-ansi_637.c

2011-04-04 Thread Bill Meier
In the proto_reg_handoff_ansi_637() code the variable 'ansi_637_trans_app_handle' is set but never used. (Coverity 835). My suspicion is that this handle should be used in the following iso 'ansi_637_trans_handle': /* Dissect messages embedded in SIP */ dissector_add_string("media_type

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

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

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

2011-04-04 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/2297 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 OSX-10.5-x86

2011-04-04 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/2729 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Bui

Re: [Wireshark-dev] setting up for win32 development

2011-04-04 Thread Stephen Fisher
On Mon, Apr 04, 2011 at 10:52:55AM +0200, Chaswi Przellczyk wrote: > I've checked my own win-setup.sh and found that lines are indeed > terminated with 0x0A (unix-standard) instead of 0x0D0A (dos and > windows standard). The compressed source code files are generatd on a Unix machine, so they

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

2011-04-04 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/2361 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-04-04 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/2723 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Bui

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

2011-04-04 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/2289 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.6-x64 Build Reason: Bui

Re: [Wireshark-dev] setting up for win32 development

2011-04-04 Thread Chaswi Przellczyk
Original-Nachricht > Datum: Mon, 4 Apr 2011 17:27:30 +1000 > Von: Risto Paasila > An: Developer support list for Wireshark > Betreff: Re: [Wireshark-dev] setting up for win32 development > On 4 April 2011 15:37, Anders Broman wrote: > > > Risto Paasila skrev 2011-04-04 06:2

Re: [Wireshark-dev] setting up for win32 development

2011-04-04 Thread Beth
I found that my Visual Studio's SetEnv.Cmd file had bugs in it - mostly missing backslashes in paths - that I had to fix before I could run Wireshark's Makefile.nmake without errors. Not sure that's your issue, but if so it would explain why upgrading WS doesn't help. _

Re: [Wireshark-dev] setting up for win32 development

2011-04-04 Thread Risto Paasila
On 4 April 2011 17:27, Risto Paasila wrote: > On 4 April 2011 15:37, Anders Broman wrote: > >> Risto Paasila skrev 2011-04-04 06:23: >> >> Hi, >> >> I'm using >> http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html to set >> up the environment, in order to compile wireshark under

Re: [Wireshark-dev] setting up for win32 development

2011-04-04 Thread Risto Paasila
On 4 April 2011 15:37, Anders Broman wrote: > Risto Paasila skrev 2011-04-04 06:23: > > Hi, > > I'm using > http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html to set > up the environment, in order to compile wireshark under windows. > > However, while doing the verify tools check