[Wireshark-dev] error LINK2001:unresolved external symbol _ett_nds

2011-02-21 Thread saugat mitra
Hi I am compiling Wireshark 1.4.1 on Microsoft Visual C Studio 2008. I have followed the steps as suggested in the Wireshark developers Guide. Have python 2.7 and have installed the tools provided by cygwin. I am getting the following error - Creating library libwireshark.lib and object

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

2011-02-21 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/44 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build:

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

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

Re: [Wireshark-dev] error LINK2001:unresolved external symbol _ett_nds

2011-02-21 Thread news.gmane.com
saugat mitra saugat.mi...@gmail.com wrote in message news:AANLkTi=i=g+j=w7vkd9d0wobiyki5uga4c-vhkz8u...@mail.gmail.com... Hi I am compiling Wireshark 1.4.1 on Microsoft Visual C Studio 2008. I have followed the steps as suggested in the Wireshark developers Guide. Have python 2.7 and have

[Wireshark-dev] Fragmentation

2011-02-21 Thread Subhasree R
Hi, I am implementing one new protocol over TCP layer. I am implementing fragment_add_check() for fragmentation. In this protocol, there was no sequence id, i.e 4th parameter. Could you please help me how to check the upcoming packets as continous packets? In this protocol, the starting flag is

Re: [Wireshark-dev] error LINK2001:unresolved external symbol _ett_nds

2011-02-21 Thread Gerald Combs
On 2/21/11 4:36 AM, news.gmane.com wrote: AFAIR packet-ncp.c is generated with Python. Even if Python is included in Cygwin, you need to install a different (native) version. I dont't know, why this hack is necessary, but it helps. You can check, if I'm right at the size of the source

Re: [Wireshark-dev] Request to review https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4334 and https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5495

2011-02-21 Thread Jaap Keuter
Hi, Done. Thanks, Jaap On 02/21/2011 08:02 AM, Kaul wrote: I'd appreciate if someone could review and, if approved, check in the above patches. They fix some VNC encoding errors and add some more parsing. Especially the hextile is a bit problematic - it works on single packet hextile encoding

[Wireshark-dev] How should plugins handle coloring

2011-02-21 Thread Roland Knall
Hello I am currently writing a dissector plugin for a machine-safety protocol. The dissector is finished and currently I am in the, let's call it, beautifying stage. Problem is, the dissector can work across quite a few other dissectors. e.g.: normally data would arrive using a realtime

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

2011-02-21 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/49 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build:

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

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

Re: [Wireshark-dev] error LINK2001:unresolved external symbol _ett_nds

2011-02-21 Thread saugat mitra
Thanks Andy Gerald I Think the problem was something due to the build area. I did a fresh checkout and repeated the build setup steps, then the error was gone. Regards Saugat. On Tue, Feb 22, 2011 at 12:24 AM, Gerald Combs ger...@wireshark.org wrote: On 2/21/11 4:36 AM, news.gmane.com