Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows 8.1 x86

2014-07-21 Thread darkjames-ws
On Tue, Jul 22, 2014 at 01:12:40AM +0200, darkjames...@darkjames.pl wrote: > > On Sun, Jul 20, 2014 at 08:04:30PM -0400, Evan Huus wrote: > > I don't really get this - it happens inconsistently that the "fast" > > allocator takes longer to run than the "block" allocator. The fast > > allocator doe

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows 8.1 x86

2014-07-21 Thread darkjames-ws
On Sun, Jul 20, 2014 at 08:04:30PM -0400, Evan Huus wrote: > I don't really get this - it happens inconsistently that the "fast" > allocator takes longer to run than the "block" allocator. The fast > allocator does much less work, and runs substantially faster than the block > allocator everywhere

Re: [Wireshark-dev] tvb allocator (was: Re: [Wireshark-commits] master b6d20a2: Optimize reseting epan_dissect_t when filtering.)

2014-07-21 Thread darkjames-ws
Hi, On Sat, Jul 12, 2014 at 02:27:06AM +0200, B??lint R??czey wrote: > I plan using ASAN for all programs which would catch (among others) > use-after-free and reading below or over the malloc()-ed > memory area. Those can't be caught if the program uses another layer > of bulk memory allocations.

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows 8.1 x86

2014-07-21 Thread Evan Huus
On Mon, Jul 21, 2014 at 2:22 AM, Anders Broman wrote: > > Den 21 jul 2014 02:34 skrev "Evan Huus" : > > > > > On Sun, Jul 20, 2014 at 8:25 PM, Guy Harris wrote: > >> > >> > >> On Jul 20, 2014, at 5:04 PM, Evan Huus wrote: > >> > >> > I don't really get this - it happens inconsistently that the

Re: [Wireshark-dev] tvb allocator (was: Re: [Wireshark-commits] master b6d20a2: Optimize reseting epan_dissect_t when filtering.)

2014-07-21 Thread darkjames-ws
Hi, On Fri, Jul 11, 2014 at 11:12:37PM +0200, B??lint R??czey wrote: > Please provide the input data for letting others reproduce the results > or perform the performance tests on pcap files already available to > the public. I have only fake one: http://www.wireshark.org/~darkjames/tvb-opt-alloc

[Wireshark-dev] 1.12 release schedule

2014-07-21 Thread Gerald Combs
I plan to release 1.12.0rc3 tomorrow (the 22nd) followed by 1.12.0 on the 29th. If we need to hold off either release for any reason please let me know. Until now release candidate tags have been preceded by a hyphen, e.g. v1.10.0-rc1. As noted in change 2759 this causes a problem for RPM and Debi

Re: [Wireshark-dev] calculating PDU size of TCP message

2014-07-21 Thread Guy Harris
On Jul 21, 2014, at 1:46 PM, "John Dill" wrote: > I have a TCP message (that I reverse engineered) that contains blocks of the > following type: > > - > | Data Type | 4 bytes > - > | Payload Len | 4 bytes > - > | Checksum | 4 bytes > - >

[Wireshark-dev] calculating PDU size of TCP message

2014-07-21 Thread John Dill
I have a TCP message (that I reverse engineered) that contains blocks of the following type: - | Data Type | 4 bytes - | Payload Len | 4 bytes - | Checksum | 4 bytes - |Data | = Payload Len - (repeats) Since I did

Re: [Wireshark-dev] Problem with qtshark command line

2014-07-21 Thread Joerg Mayer
On Mon, Jul 21, 2014 at 11:07:57AM +0200, Alexis La Goutte wrote: > The help is wrong... (Copy/paste from gtk) > -i and -k option is not yet supported by qtshark OK, that explains it :-) Thanks! Jörg -- Joerg Mayer We are stuck with technology when

Re: [Wireshark-dev] Problem with qtshark command line

2014-07-21 Thread Alexis La Goutte
Hi joerg The help is wrong... (Copy/paste from gtk) -i and -k option is not yet supported by qtshark I have start a patch but need more time to work... Le lundi 21 juillet 2014, Joerg Mayer a écrit : > Hello, > > the following works with wireshark but not qtshark: > > jmayer@egg:~/work/wiresh