Re: [Wireshark-dev] display of TLVs in MIH protocol dissector

2011-07-11 Thread Ankith Agarwal
Hi, Thank you for the advice, it was very helpful... Regards Ankith On Mon, Jul 11, 2011, Jaap Keuter said: > Hi, > > You could take a look at the CDP dissector: > http://anonsvn.wireshark.org/wireshark/trunk/epan/dissectors/packet-cdp.c > > It has basically the same problem, which it so

Re: [Wireshark-dev] Procedure to compile wireshark dissector on linux

2011-07-11 Thread Tony Trinh
I like the CMake build better (easier to use and 'pretty') except for the verbose output, which is masochistically enabled by default. There's a commentthat suggests the verboseness was meant to be temporary:

Re: [Wireshark-dev] UTF8 vs. locale in error messages (bug 5715)

2011-07-11 Thread Guy Harris
On Jul 11, 2011, at 4:00 PM, Stephen Fisher wrote: > The popular SecureCRT terminal emulator defaults to "default" (same as > local system) character encoding, at least on Windows systems. This is > not compatible with UTF-8 in my experience. Not surprising, given that "default"/"same as loca

Re: [Wireshark-dev] Autodetection of file types

2011-07-11 Thread Stephen Fisher
On Fri, Jul 01, 2011 at 03:07:19PM +, Matt Godbolt wrote: > From looking at the source, the packetlogger_open() call doesn't to > seem to be very restrictive - I can see how it could generate false > positives. I can also see from file_access.c that packetlogger files > have sometimes been

Re: [Wireshark-dev] UTF8 vs. locale in error messages (bug 5715)

2011-07-11 Thread Stephen Fisher
On Tue, Jun 28, 2011 at 10:01:14AM -0700, Guy Harris wrote: > I don't know what the various terminal emulators for Windows, e.g. > cmd.exe, do. The popular SecureCRT terminal emulator defaults to "default" (same as local system) character encoding, at least on Windows systems. This is not com

[Wireshark-dev] How not to compile unwanted plugins

2011-07-11 Thread eymanm
I used to comment out unwanted plugins in the \plugin\Makefile.nmake file to avoid plugins that not needed in the build. This seems not to work in 1.6.0. Wireshark crashes immediately on startup indicating "request the runtime to terminate". Can somebody suggest how to make it right in v1.6.0 on w

Re: [Wireshark-dev] How to build on MACOS

2011-07-11 Thread Gerald Combs
On 7/11/11 2:39 PM, Stephen Fisher wrote: > On Sun, Jun 19, 2011 at 10:28:37AM -0700, Guy Harris wrote: > >> Also, do you need PCRE with newer versions of GLib? I think we use >> GLib's PCRE routines if available. > > The last time I compiled GLib, I realized that it requires PCRE for > regex

Re: [Wireshark-dev] How to build on MACOS

2011-07-11 Thread Stephen Fisher
On Sun, Jun 19, 2011 at 10:28:37AM -0700, Guy Harris wrote: > Also, do you need PCRE with newer versions of GLib? I think we use > GLib's PCRE routines if available. The last time I compiled GLib, I realized that it requires PCRE for regex support, so all we did by switching to GLib's regex is

Re: [Wireshark-dev] Handing off payloads to the TCP dissector?

2011-07-11 Thread Stephen Fisher
On Sun, Jun 19, 2011 at 01:59:21AM +0100, Tyson Key wrote: > I'm currently in the process of writing a dissector for Apple's USBMUX > protocol (which encapsulates TCP frames with a non-IP-based 8 byte > header), as used by their seemingly ubiquitous iProduct family. > Having looked at the IPv4

[Wireshark-dev] buildbot failure in Wireshark (development) on Ubuntu-10.04-x64

2011-07-11 Thread buildbot-no-reply
The Buildbot has detected a new failure of Ubuntu-10.04-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-10.04-x64/builds/1720 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-10.04-x64 Build

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

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

Re: [Wireshark-dev] XMPP dissector

2011-07-11 Thread Mariusz Okrój
Thanks for answer. 2011/7/11 Stig Bjørlykke : > 1. It does not compile: > > Making all in xmpp >  CC     xmpp.lo > xmpp.c: In function 'xml_frame_to_element_t': > xmpp.c:360: error: dereferencing pointer to incomplete type > xmpp.c:385: error: dereferencing pointer to incomplete type > xmpp.c: In

[Wireshark-dev] Fwd: [Wireshark-commits] rev 37967: /trunk/ /trunk/: configure.in

2011-07-11 Thread Gerald Combs
All, The minimum supported GLib and GTK+ versions in /trunk are 2.14 and 2.12, respectively. Original Message Subject: [Wireshark-commits] rev 37967: /trunk/ /trunk/: configure.in Date: Mon, 11 Jul 2011 17:50:02 GMT From: ger...@wireshark.org Reply-To: wireshark-dev@wireshark.o

Re: [Wireshark-dev] Makefile for wireshark dissector

2011-07-11 Thread Guy Harris
On Jul 11, 2011, at 4:38 AM, sagar sg wrote: > the question i have is the code i have written is in C++, See http://wsgd.free.fr/ for an example of a Wireshark plugin written in C++. ___ Sent via:Wireshark-dev

Re: [Wireshark-dev] XMPP dissector

2011-07-11 Thread Stig Bjørlykke
2011/7/8 Mariusz Okrój : > It would be really great to get feedback from you. 1. It does not compile: Making all in xmpp CC xmpp.lo xmpp.c: In function 'xml_frame_to_element_t': xmpp.c:360: error: dereferencing pointer to incomplete type xmpp.c:385: error: dereferencing pointer to incomplet

Re: [Wireshark-dev] Makefile for wireshark dissector

2011-07-11 Thread Jaap Keuter
Hi, You can find all instructions in README.plugins: http://anonsvn.wireshark.org/wireshark/trunk/doc/README.plugins As for C++ code, the Wireshark is a C only project, you should read up on the portability guidelines in README.developer: http://anonsvn.wireshark.org/wireshark/trunk/doc/README

Re: [Wireshark-dev] display of TLVs in MIH protocol dissector

2011-07-11 Thread Jaap Keuter
Hi, You could take a look at the CDP dissector: http://anonsvn.wireshark.org/wireshark/trunk/epan/dissectors/packet-cdp.c It has basically the same problem, which it solves by re-using the ett value. Thanks, jaap On Mon, 11 Jul 2011 14:22:51 +0530 (IST), Ankith Agarwal wrote: Hi I am writi

Re: [Wireshark-dev] Makefile for wireshark dissector

2011-07-11 Thread sagar sg
ya, but can we change the CC flag by GCC in Makefile.nmake because as i know GCC can compile C source. On Mon, Jul 11, 2011 at 5:28 PM, Ankith Agarwal wrote: > Hi > I don't have much experience with this... > On Mon, Jul 11, 2011, sagar sg said: > > > Hi Ankit, > > Thank you very

Re: [Wireshark-dev] Makefile for wireshark dissector

2011-07-11 Thread Ankith Agarwal
Hi I don't have much experience with this... On Mon, Jul 11, 2011, sagar sg said: > Hi Ankit, > Thank you very much Ankit, I 'm trying to follow the 1st > method. the question i have is the code i have written is in C++, i guess > the wireshark is compiled with CC ,Does CC can com

Re: [Wireshark-dev] Makefile for wireshark dissector

2011-07-11 Thread sagar sg
Hi Ankit, Thank you very much Ankit, I 'm trying to follow the 1st method. the question i have is the code i have written is in C++, i guess the wireshark is compiled with CC ,Does CC can compile the C++ code, i have used C style of C++ without much OOPS concepts. Thanks and Regards S

Re: [Wireshark-dev] Makefile for wireshark dissector

2011-07-11 Thread Ankith Agarwal
On Mon, Jul 11, 2011, sagar sg said: > Hi, > I have written a dissector plug in in windows and it works fine, now i > want to compile it in linux to get the .so file, please help me how do i > write a make file for the wireshark dissector. i got one example file but > there i saw something

[Wireshark-dev] buildbot failure in Wireshark (development) on Ubuntu-10.04-x64

2011-07-11 Thread buildbot-no-reply
The Buildbot has detected a new failure of Ubuntu-10.04-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-10.04-x64/builds/1714 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-10.04-x64 Build

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

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

Re: [Wireshark-dev] Procedure to compile wireshark dissector on linux

2011-07-11 Thread sagar sg
I did build the wireshark already, now i want to build my dissector either by creating a shared library or any other way. how do i do that ? i have my dissector code already which works fine on windows. On Mon, Jul 11, 2011 at 3:33 PM, Ed Beroset wrote: > sagar sg wrote: > >> Hi, >> What is

Re: [Wireshark-dev] Procedure to compile wireshark dissector on linux

2011-07-11 Thread sagar sg
Where should i keep my dissector Code.? Regards sagar On Mon, Jul 11, 2011 at 3:33 PM, Roland Knall wrote: > Hi > > Way easier method: > > Checkout the SVN version, or any source download into one dir called > src. Create a same directory called build on the same level, so that > your directory

Re: [Wireshark-dev] Procedure to compile wireshark dissector on linux

2011-07-11 Thread Roland Knall
Hi Way easier method: Checkout the SVN version, or any source download into one dir called src. Create a same directory called build on the same level, so that your directory looks like that: - src - - build then goto build, and call cmake ../src cmake is a software distributed with al

Re: [Wireshark-dev] Procedure to compile wireshark dissector on linux

2011-07-11 Thread Ed Beroset
sagar sg wrote: Hi, What is the procedure for compiling the wireshark dissector in linux. http://www.wireshark.org/docs/wsdg_html_chunked/ChSrcBuildFirstTime.html#id521996 Ed ___ Sent via:Wireshark-dev mailing li

[Wireshark-dev] Procedure to compile wireshark dissector on linux

2011-07-11 Thread sagar sg
Hi, What is the procedure for compiling the wireshark dissector in linux. Thanks Sagar ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.

[Wireshark-dev] Makefile for wireshark dissector

2011-07-11 Thread sagar sg
Hi, I have written a dissector plug in in windows and it works fine, now i want to compile it in linux to get the .so file, please help me how do i write a make file for the wireshark dissector. i got one example file but there i saw something like .TSN compiler which i dint understand of how

[Wireshark-dev] Makefile for wireshark dissector

2011-07-11 Thread sagar sg
Hi, I have written a dissector plug in in windows and it works fine, now i want to compile it in linux to get the .so file, please help me how do i write a make file for the wireshark dissector. i got one example file but there i something like .TSN compiler and all and i dint understand how i

[Wireshark-dev] display of TLVs in MIH protocol dissector

2011-07-11 Thread Ankith Agarwal
Hi I am writing a plugin for dissection of MIH protocol. https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6547 This protocol contains all the information in form of TLVs(type length value), also this protocol does not specify the maximum number of TLVs inside a packet. I am confused in the