[Wireshark-dev] Static analysis added to the buildbot

2011-02-15 Thread Gerald Combs
The trunk buildbot now has two additional buildslaves: one that runs the C/C++ code analyzer in Visual Studio 10 Premium and one that runs the Clang Static Analyzer. They are scheduled to run once a day at 9:00 PM PST (5:00 AM UTC) for the time being. Scan-build creates very large (about 3 GB unco

Re: [Wireshark-dev] libwireshark.lib is missing some proto_registrar_* methods

2011-02-15 Thread Andreas
Am 11.02.2011 12:36, schrieb Ed Beroset: Andreas wrote: Am 11.02.2011 00:06, schrieb Guy Harris: > They weren't omitted on purpose. They were probably omitted because > they were added by a UN*X user; by default, UN*X dynamic shared > libraries export every non-static symbol, unlike Windows DLLs

Re: [Wireshark-dev] digging something meaningful out of xmlrpc

2011-02-15 Thread Toni Ruottu
Thank you for the tip. However my problem is not so much about being able to do the job of parsing the XML. It is a more a philosophical/API question. Is it ok to dissect something in a way that leaves lots of bytes unexplained? Also, is it possible to show a more general and a less general dessect

Re: [Wireshark-dev] FW: [Wireshark-commits] rev 35946: /trunk/ /trunk/: config.nmake -> compile fails.

2011-02-15 Thread Bill Meier
On 2/15/2011 11:25 AM, Bill Meier wrote: Gerald: I expect you meant to remove the # from the !IFDEF & !ENDIF ... #!IFDEF ENABLE_CODE_ANALYSIS LOCAL_CFLAGS= $(LOCAL_CFLAGS) /analyze:WX- #!ENDIF I committed this change in SVN #35951:) Bill _

Re: [Wireshark-dev] digging something meaningful out of xmlrpc

2011-02-15 Thread David Young
On Tue, Feb 15, 2011 at 03:05:47PM +0200, Toni Ruottu wrote: > I am using Wireshark to analyse services that use XML-RPC calls to > communicate. Currently the protocol gets dissected as XML which is > fine because it is XML. However the result has lots of bloat that > makes it hard for me to analys

Re: [Wireshark-dev] FW: [Wireshark-commits] rev 35946: /trunk/ /trunk/: config.nmake -> compile fails.

2011-02-15 Thread Bill Meier
User: gerald Date: 2011/02/14 10:58 AM Log: Enable Enterprise Code Analysis via the ENABLE_CODE_ANALYSIS environment variable. Directory: /trunk/ ChangesPathAction +2 -2 config.nmakeModified Gerald: I expect you meant to remove the # from the !IFDEF & !END

[Wireshark-dev] digging something meaningful out of xmlrpc

2011-02-15 Thread Toni Ruottu
I am using Wireshark to analyse services that use XML-RPC calls to communicate. Currently the protocol gets dissected as XML which is fine because it is XML. However the result has lots of bloat that makes it hard for me to analyse the protocol built on top of XML-RPC. Can I somehow write a dissect

[Wireshark-dev] FW: [Wireshark-commits] rev 35946: /trunk/ /trunk/: config.nmake -> compile fails.

2011-02-15 Thread Anders Broman
Hi, My compiler barfs on this setting :-( C:\Wireshark-trunk>nmake -f makefile.nmake Microsoft (R) Program Maintenance Utility Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. Verifying library package files ... Microsoft (R) Program Maintenance Utility Version 9.