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

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

Re: [Wireshark-dev] Having the buildbot build Wireshark 64-bit for Mac OS X (was Re: [Wireshark-bugs] [Bug 4115] 32-bit Wireshark crashes while opening large trace files)

On Apr 27, 2010, at 5:41 PM, Jeff Morriss wrote: > On Tue, Apr 27, 2010 at 4:05 PM, Guy Harris wrote: >> >> On Apr 27, 2010, at 12:37 PM, Jeff Morriss wrote: >>> But: would the header files have to be different? Linux and Solaris >>> seem get away with one set of header files for both the 32-

Re: [Wireshark-dev] Having the buildbot build Wireshark 64-bit for Mac OS X (was Re: [Wireshark-bugs] [Bug 4115] 32-bit Wireshark crashes while opening large trace files)

On Tue, Apr 27, 2010 at 4:05 PM, Guy Harris wrote: > > On Apr 27, 2010, at 12:37 PM, Jeff Morriss wrote: >> But: would the header files have to be different?  Linux and Solaris >> seem get away with one set of header files for both the 32- and 64-bit >> libraries. > > I'm not sure how they handle

Re: [Wireshark-dev] Parsing variable length protocol trailer

On Tue, Apr 27, 2010 at 12:22:14PM -0700, Edgar, Thomas wrote: > Is there a way to determine how many bytes the subdissectors actually > used or how many bytes are left unused after a return from > dissector_try_port/heuristic? If you were using call_dissector(), which lets you call a (sub-)di

Re: [Wireshark-dev] Parsing variable length protocol trailer

For those types of dissectors called in that manner, I don't know of any way directly to tell how many bytes were dissected, but you could have the calling dissector initialize a pinfo->private_data struct that contains a "number of bytes dissected" field initialized to zero. Before the subdiss

Re: [Wireshark-dev] DISSECTOR_SUPPORT_SRC in another directory in Windows

Well, it looks like the problem is that when the plugins/plugin-common/support_file.c file is compiled, the resulting support_file.obj is saved to plugins/plugin_directory/support_file.obj, so when the linker looks for the object file in the same directory as the source file, it can't find it.

Re: [Wireshark-dev] Having the buildbot build Wireshark 64-bit for Mac OS X (was Re: [Wireshark-bugs] [Bug 4115] 32-bit Wireshark crashes while opening large trace files)

On Apr 27, 2010, at 10:27 PM, Guy Harris wrote: > > On Apr 27, 2010, at 1:20 PM, Michael Tüxen wrote: > >> The intel and ppc buildbots currently run Leopard and build 32-bit >> applications. >> >> I can update the intel buildbot to SnowLeopard and rebuild the required >> libs. Then we would hav

Re: [Wireshark-dev] Having the buildbot build Wireshark 64-bit for Mac OS X (was Re: [Wireshark-bugs] [Bug 4115] 32-bit Wireshark crashes while opening large trace files)

On Apr 27, 2010, at 1:20 PM, Michael Tüxen wrote: > The intel and ppc buildbots currently run Leopard and build 32-bit > applications. > > I can update the intel buildbot to SnowLeopard and rebuild the required > libs. Then we would have a 64-bit version. ...which probably wouldn't, by default,

Re: [Wireshark-dev] Having the buildbot build Wireshark 64-bit for Mac OS X (was Re: [Wireshark-bugs] [Bug 4115] 32-bit Wireshark crashes while opening large trace files)

On Apr 27, 2010, at 9:37 PM, Jeff Morriss wrote: > Guy Harris wrote: >> On Apr 27, 2010, at 11:36 AM, Jeff Morriss wrote: >> >>> Given that the MacOS buildbot (at least the Intel one) is so fast, would >>> it make sense to also build a 64-bit version of Wireshark? >> >> As long as we make sure

Re: [Wireshark-dev] Having the buildbot build Wireshark 64-bit for Mac OS X (was Re: [Wireshark-bugs] [Bug 4115] 32-bit Wireshark crashes while opening large trace files)

On Apr 27, 2010, at 12:37 PM, Jeff Morriss wrote: > Guy Harris wrote: >> On Apr 27, 2010, at 11:36 AM, Jeff Morriss wrote: >> >>> Given that the MacOS buildbot (at least the Intel one) is so fast, would >>> it make sense to also build a 64-bit version of Wireshark? >> >> As long as we make sur

Re: [Wireshark-dev] Having the buildbot build Wireshark 64-bit for Mac OS X (was Re: [Wireshark-bugs] [Bug 4115] 32-bit Wireshark crashes while opening large trace files)

Guy Harris wrote: > On Apr 27, 2010, at 11:36 AM, Jeff Morriss wrote: > >> Given that the MacOS buildbot (at least the Intel one) is so fast, would >> it make sense to also build a 64-bit version of Wireshark? > > As long as we make sure it works on Leopard before we offer it to Leopard > users

Re: [Wireshark-dev] DISSECTOR_SUPPORT_SRC in another directory in Windows

OK, but if your header files are not in the directories already included, then you'll need to add an additional /I$(SOME_PATH) directive to CFLAGS so they can be found. - Chris -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On

[Wireshark-dev] Parsing variable length protocol trailer

I have a variable length protocol trailer (which is only known by the end devices) to parse and there is no way to figure it out during the framing process. Is there a way to determine how many bytes the subdissectors actually used or how many bytes are left unused after a return from dissecto

Re: [Wireshark-dev] DISSECTOR_SUPPORT_SRC in another directory in Windows

On Tue, Apr 27, 2010 at 11:27, Maynard, Chris wrote: > What does your directory structure look like?  i.e., is common/ under > plugins/ or off the root?  It looks to me like Windows is looking for common/ > path-relative to your plugin directory so you should have > "wireshark/plugins/common/su

[Wireshark-dev] Having the buildbot build Wireshark 64-bit for Mac OS X (was Re: [Wireshark-bugs] [Bug 4115] 32-bit Wireshark crashes while opening large trace files)

On Apr 27, 2010, at 11:36 AM, Jeff Morriss wrote: > Given that the MacOS buildbot (at least the Intel one) is so fast, would > it make sense to also build a 64-bit version of Wireshark? As long as we make sure it works on Leopard before we offer it to Leopard users. The BPF in Leopard, as I r

Re: [Wireshark-dev] DISSECTOR_SUPPORT_SRC in another directory in Windows

On Tue, Apr 27, 2010 at 11:35, Maynard, Chris wrote: > What does your plugin's CFLAGS look like in Makefile.nmake?  And where are > your header files that you're trying to #include? My CFLAGS are the same as the CFLAGS in the asn1 plugin. I just copied that file as a base for my plugin.

Re: [Wireshark-dev] [Wireshark-bugs] [Bug 4115] 32-bit Wireshark crashes while opening large trace files

bugzilla-dae...@wireshark.org wrote: > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4115 > > --- Comment #20 from Jeff Morriss 2010-04-27 > 11:00:48 PDT --- > (In reply to comment #18) >>> Is this a 32- or 64-bit process? (Running 'file' on the wireshark >>> executable >>> should tell y

Re: [Wireshark-dev] cannot load the module error

Using VS2008 is the best solution. If it is not possible. For runtime error R6034, you can also look at : - http://msdn.microsoft.com/en-us/library/ms235560%28VS.80%29.aspx For the msvcr80.dll problem, see : - http://www.microsoft.com/downloads/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b

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

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/108 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-ppc Build Reaso

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

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

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

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/109 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

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

Re: [Wireshark-dev] Problem during compilation

“I'll probably put VS2008 Express in a VM (or use a linux VM) for compiling Wireshark in which case the problem will be fixed for me.” … at least until we switch to VS2010 ☺ - Chris CONFIDENTIALITY NOTICE: The contents of this email are confidential and for the exclusive use of the intended reci

Re: [Wireshark-dev] Problem during compilation

On 27/04/2010 16:39, Maynard, Chris wrote: > > Hi Graham, > > While I don’t compile with VS2005, obviously many folks still do. If > you ever do have the time, it would probably be beneficial to others > if you would post your patches, either here on –dev or through bugzilla. > > Thanks. > > - Chr

Re: [Wireshark-dev] Problem during compilation

Hi Graham, While I don’t compile with VS2005, obviously many folks still do. If you ever do have the time, it would probably be beneficial to others if you would post your patches, either here on –dev or through bugzilla. Thanks. - Chris From: wireshark-dev-boun...@wireshark.org [mailto:wires

Re: [Wireshark-dev] DISSECTOR_SUPPORT_SRC in another directory in Windows

What does your plugin's CFLAGS look like in Makefile.nmake? And where are your header files that you're trying to #include? - Chris -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jeremy O'Brien Sent: Tuesday, April

Re: [Wireshark-dev] DISSECTOR_SUPPORT_SRC in another directory in Windows

What does your directory structure look like? i.e., is common/ under plugins/ or off the root? It looks to me like Windows is looking for common/ path-relative to your plugin directory so you should have "wireshark/plugins/common/support_file.c". If you want to keep the directory structure a

Re: [Wireshark-dev] Runtime Error while starting wireshark 1.3.4 with "MATE" configured

Thanks a lot for your support. Mate is working quite well now with the Version I downloaded from your link. Regards, Marcel OnePhone Marcel Sicking - Core Network Engineer Tel: +49 (211) 5423 5010 Mobil: +49 (1577) 540 5010 Fax: +49 (211) 5423 5099 E-Mail: marcel.sick...@onephone.de Web: http:

Re: [Wireshark-dev] About Wiretap Library

> > I need to capture iSCSI packets (using tshark) and then open the capture > files and get the data I need using a dissector to analise it. > > Note that libpcap/Winpcap *AND* Wiretap both just give you raw packet data; > they do not do *any* dissection. > > I know that libpcap / Wiretap just giv

Re: [Wireshark-dev] DISSECTOR_SUPPORT_SRC in another directory in Windows

Also, I can't seem to use relative paths for #include either. What gives? On Tue, Apr 27, 2010 at 09:44, Jeremy O'Brien wrote: > Yeah I tried changing it to "\" and "\\", neither of which worked. :( > > On Sun, Apr 25, 2010 at 14:43, Maynard, Chris > wrote: >> Just a guess, but maybe it's due to

Re: [Wireshark-dev] DISSECTOR_SUPPORT_SRC in another directory in Windows

Yeah I tried changing it to "\" and "\\", neither of which worked. :( On Sun, Apr 25, 2010 at 14:43, Maynard, Chris wrote: > Just a guess, but maybe it's due to the different path separator ... i.e., > '/' for *nix vs. '\' for Windows? > - Chris > > From:

Re: [Wireshark-dev] RFC: sorted value_string + bsearch

Committed revision 32576. -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jakub Zawadzki Sent: den 27 april 2010 13:29 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] RFC: sorted value_string + b

Re: [Wireshark-dev] RFC: sorted value_string + bsearch

On Tue, Apr 27, 2010 at 12:34:14PM +0200, Anders Broman wrote: > Committed revision 32574 to faciliate further testing, dockumentation updates > will be needed if/when we are > happy with the implementation. Thx. I have two changes in implementation :) - use function pointers instead of switch.

Re: [Wireshark-dev] cannot load the module error

On 27/04/2010 11:19, ankur madan wrote: > I have downloaded version 1.2.7 and installed it separatelly and i > have copied the dllat *c:\program files\wireshark*. > i have build version of wiresshark at *c:\wireshark*,through which i > created my own dissector. > so i copied the dll from *c:\wiresh

Re: [Wireshark-dev] RFC: sorted value_string + bsearch

Hi, Committed revision 32574 to faciliate further testing, dockumentation updates will be needed if/when we are happy with the implementation. Regards Anders -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jakub Zawa

Re: [Wireshark-dev] cannot load the module error

I have downloaded version 1.2.7 and installed it separatelly and i have copied the dllat *c:\program files\wireshark*. i have build version of wiresshark at *c:\wireshark*,through which i created my own dissector. so i copied the dll from *c:\wireshark\plugins to c:\program files\wireshark\plugins\

Re: [Wireshark-dev] cannot load the module error

On 27/04/2010 11:05, ankur madan wrote: > Hi, > i created my own dissector "dissbill".i created the dll and > manifest of this plugin and copied it to c:\program > files\wireshark\plugin.after that i run tshark.exe though cmd.it > gave me the error,could not load the module and

[Wireshark-dev] cannot load the module error

Hi, i created my own dissector "dissbill".i created the dll and manifest of this plugin and copied it to c:\program files\wireshark\plugin.after that i run tshark.exe though cmd.it gave me the error,could not load the module and msvcr80.dll not found. after this i copied msvcr80.dll to system32

Re: [Wireshark-dev] Problem during compilation

thanks graham,it worked for me.its compiling successfully thanks ankur On Tue, Apr 27, 2010 at 2:26 PM, Graham Bloice wrote: > On 27/04/2010 05:38, ankur madan wrote: > > So,is there any other solution for this problem.due to some reason i have 2 > work on VS 2005 only.looking forward for a res

Re: [Wireshark-dev] Problem during compilation

On 27/04/2010 05:38, ankur madan wrote: > So,is there any other solution for this problem.due to some reason i > have 2 work on VS 2005 only.looking forward for a response. > There are three main issues you will face when trying to compile Wireshark with VS2005: 1) The makefiles and sources attem

Re: [Wireshark-dev] RFC: sorted value_string + bsearch

On Tue, Apr 27, 2010 at 09:53:36AM +0200, Anders Broman wrote: > I'll try - busy right now - > Could you re send the patch proto.c just got updated. Attached. I've also fixed: - if ((hfinfo->display & BASE_EXT_STRING) == 0) { + if ((hfin

Re: [Wireshark-dev] Dissecting a Protocol with multiple static TCP ports

On Mon, Apr 26, 2010 at 10:15:01PM -0700, Craig Bumpstead wrote: > So your saying to reassemble the packet then run the dissector again? At the beginning of your dissection, figure out if the packet is going to span multiple TCP segments. If it is, return to Wireshark with information on how m

Re: [Wireshark-dev] Problem during compilation

On Apr 26, 2010, at 9:38 PM, ankur madan wrote: > So,is there any other solution for this problem. Use the latest version from SVN; I checked in a change that should fix the compiler warnings. ___ Sent via:Wireshark-dev

Re: [Wireshark-dev] Problem during compilation

On Apr 26, 2010, at 2:35 AM, Graham Bloice wrote: > IMHO the current code is incorrect as it incorrectly casts a 32 bit value to > a 64 bit one and then calls proto_tree_add_uint64 with it when the value > really is a 32 bit one (lines 981-985): > > if (packet->key_id_mode == KEY_ID_MO

Re: [Wireshark-dev] RFC: sorted value_string + bsearch

Hi, I'll try - busy right now - Could you re send the patch proto.c just got updated. Regards Anders -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jakub Zawadzki Sent: den 27 april 2010 08:49 To: Developer support

Re: [Wireshark-dev] RFC: sorted value_string + bsearch

On Tue, Apr 27, 2010 at 08:49:23AM +0200, Jakub Zawadzki wrote: > On Tue, Apr 27, 2010 at 08:15:35AM +0200, Anders Broman wrote: > > Can you provide an example use of the new value_string_ext as well? > > Can you do some benchmarks? :) mine, only dns packets: Number of packets: 504 Average

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

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/104 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

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