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
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
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.
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
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
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
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
> -
>
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
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
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
10 matches
Mail list logo