[Wireshark-dev] WiresharkXML.py

Hi, I'm trying to build a Jenkins job which tests if my own dissector is working well. Therefore i decided to use tshark and safe the results in a pdml file, which i want to check with a python script. At the moment i only want to get the name and the value of the single attributes in my pdml

Re: [Wireshark-dev] 1.99.0 release

On Wed, Oct 1, 2014 at 1:41 AM, Gerald Combs wrote: > I've scheduled the release of 1.99.0 for next Tuesday, October 7. Nice, it is for 1 year of official migration to Qt ? ;-) > Corrections and additions for the release notes are welcome. > > Depending on how well the Mac OS X packages work I mi

Re: [Wireshark-dev] Compiling wirehsark --treat all warnings as errors.

On Sep 30, 2014, at 4:44 PM, Ateeth Kumar wrote: > I used a system call in unix to run a process from wireshark toolbar. > > However during compilation time the gcc compiler treats all warnings as > errors. ... > error: ignoring return value of ‘system’, declared with attribute > w

Re: [Wireshark-dev] Building Wireshark on MAC

On 9/30/14 3:20 PM, Anders Broman wrote: > > Den 30 sep 2014 23:01 skrev "Guy Harris" >: >> >> >> On Sep 25, 2014, at 1:31 PM, Guy Harris > wrote: >> >> > On Sep 25, 2014, at 1:25 PM, Anders Broman > wrote: >> > >>

[Wireshark-dev] 1.99.0 release

I've scheduled the release of 1.99.0 for next Tuesday, October 7. Corrections and additions for the release notes are welcome. Depending on how well the Mac OS X packages work I might add a note to the stable and old stable sections on the download page recommending that OS X users use the develop

[Wireshark-dev] Compiling wirehsark --treat all warnings as errors.

I used a system call in unix to run a process from wireshark toolbar. However during compilation time the gcc compiler treats all warnings as errors. Is there a way I can ignore warnings and let wireshark compile? error: ignoring return value of ‘system’, declared with attribute warn_unused_resul

Re: [Wireshark-dev] Building Wireshark on MAC

Den 30 sep 2014 23:01 skrev "Guy Harris" : > > > On Sep 25, 2014, at 1:31 PM, Guy Harris wrote: > > > On Sep 25, 2014, at 1:25 PM, Anders Broman wrote: > > > >> Configure fails though, without parameters > >> : > >> checking for pkg-config... /usr/local/bin/pkg-config > >> checking for Qt5Core -

Re: [Wireshark-dev] FW: [Wireshark-commits] master 5330875: GTK+: Revert back to 2.24.14-1.1 on Win64.

On 9/30/14 12:30 PM, Anders Broman wrote: > > Den 30 sep 2014 21:27 skrev "Gerald Combs" >: >> >> On 9/30/14 5:00 AM, Anders Broman wrote: >> > >> >> Switching to the OBS GTK+ 3.14 package. It looks like a lot of > our GTK+ code is >> >>deprecated, including

Re: [Wireshark-dev] Building Wireshark on MAC

On Tuesday 30 September 2014 21:36:33 Anders Broman wrote: > Ok that was helpful, unfortunately the result is: > > -- The following OPTIONAL packages have not been found: > > > * CAP > > * GTK3 > > * Qt5LinguistTools > > * Qt5MacExtras > > * Qt5PrintSupport > > * Qt5Widgets > > * SB

Re: [Wireshark-dev] Building Wireshark on MAC

On Sep 25, 2014, at 1:31 PM, Guy Harris wrote: > On Sep 25, 2014, at 1:25 PM, Anders Broman wrote: > >> Configure fails though, without parameters >> : >> checking for pkg-config... /usr/local/bin/pkg-config >> checking for Qt5Core - version >= 4.6.0... no >> checking for QtCore - version >= 4

Re: [Wireshark-dev] GTK+: Revert back to 2.24.14-1.1 on Win64.

Correct. Is there a reason we don't use a unique name for the GTK+ library directory, e.g. "gtk-2.24.23-1.1-win64ws" instead of "gtk2"? It seems like that would avoid this sort of problem and simplify the Nmake files a bit. On 9/30/14 12:39 PM, Anders Broman wrote: > But if I don't rerun setup I w

Re: [Wireshark-dev] 'Virtual' subtree

Thanks guys, I will give it a try. On Tue, Sep 30, 2014 at 1:03 PM, wrote: > You can group fields in whatever way makes sense for your protocol, it > doesn't always have to be flat or a "real" field (or a "real" structure). > I would think that you would just call proto_tree_add_subtree() and pa

Re: [Wireshark-dev] GTK+: Revert back to 2.24.14-1.1 on Win64.

But if I don't rerun setup I will build with the old GTK bundle, as that's what's unpacked into GTK dir - right? 2014-09-30 21:22 GMT+02:00 Gerald Combs : > On 9/30/14 4:54 AM, Anders Broman wrote: > > Hi, > > > > Don’t we need a new setup TAG as well for this to take effect? > > gtk+-bundle_2.24

Re: [Wireshark-dev] FW: [Wireshark-commits] master 5330875: GTK+: Revert back to 2.24.14-1.1 on Win64.

Den 30 sep 2014 21:27 skrev "Gerald Combs" : > > On 9/30/14 5:00 AM, Anders Broman wrote: > > > >> Switching to the OBS GTK+ 3.14 package. It looks like a lot of our GTK+ code is > >>deprecated, including GtkAction and GtkAttachOptions. > >Would using 3.14 work if we remove on or more

Re: [Wireshark-dev] FW: [Wireshark-commits] master 5330875: GTK+: Revert back to 2.24.14-1.1 on Win64.

On 9/30/14 5:00 AM, Anders Broman wrote: > >> Switching to the OBS GTK+ 3.14 package. It looks like a lot of our GTK+ >> code is >>deprecated, including GtkAction and GtkAttachOptions. >Would using 3.14 work if we remove on or more of these flags from > config.nmake? > -DGDK_D

Re: [Wireshark-dev] GTK+: Revert back to 2.24.14-1.1 on Win64.

On 9/30/14 4:54 AM, Anders Broman wrote: > Hi, > > Don’t we need a new setup TAG as well for this to take effect? gtk+-bundle_2.24.14-1.1_win64ws.zip wasn't removed from the repository before tags/2014-07-27 was created, so it's part of that tag: http://anonsvn.wireshark.org/wireshark-win64-libs

Re: [Wireshark-dev] 'Virtual' subtree

You can group fields in whatever way makes sense for your protocol, it doesn't always have to be flat or a "real" field (or a "real" structure). I would think that you would just call proto_tree_add_subtree() and pass it the title of or . You may have to call proto_item_set_len later on the

Re: [Wireshark-dev] 'Virtual' subtree

You can use a proto_tree_add_item with BASE_NONE and length = 0 (and add a subtree after...) Regards, On Tue, Sep 30, 2014 at 2:01 PM, Simon Zhong wrote: > Hi, > I'm working on PCEP dissector, I'm wonder if it's possible to create a > 'virtual' subtree. > The format of a message is as follows: >

[Wireshark-dev] 'Virtual' subtree

Hi, I'm working on PCEP dissector, I'm wonder if it's possible to create a 'virtual' subtree. The format of a message is as follows: ::= [] where: ::=[] ::=[] ::= [] [] []

[Wireshark-dev] FW: [Wireshark-commits] master 5330875: GTK+: Revert back to 2.24.14-1.1 on Win64.

> Switching to the OBS GTK+ 3.14 package. It looks like a lot of our GTK+ > code is >deprecated, including GtkAction and GtkAttachOptions. Would using 3.14 work if we remove on or more of these flags from config.nmake? -DGDK_DISABLE_DEPRECATED \ -DGDK_PIXBUF_DISABLE_D

[Wireshark-dev] GTK+: Revert back to 2.24.14-1.1 on Win64.

Hi, Don't we need a new setup TAG as well for this to take effect? Regards Anders ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman

Re: [Wireshark-dev] Building Wireshark on MAC

On Monday 29 September 2014 21:09:22 Anders Broman wrote: > Well for a cmake newbie it would help with an example of which parameters > to use... Typically you have a build directory separate from your code. Minimal example: mkdir build && cd build cmake $path_to_srcdir make # Bui