Wireshark-dev: Re: [Wireshark-dev] Crash with the new win32 GTK+ bundle when opening an analysi
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Evan Huus <eapache@xxxxxxxxx>
Date: Fri, 20 Apr 2012 06:43:37 -0400
There have recently been changes in the way that conversations are re-analyzed (to make them faster) that might have accidentally caused this. If the same crash happens with Flow Graph and Conversations then please file a bug with a reproducible capture - the changes worked on everything I tried, but I guess I missed a corner case somewhere.

Evan

Sent from my iPod

On 2012-04-20, at 5:58 AM, Pascal Quantin <pascal.quantin@xxxxxxxxx> wrote:

Hi all,

with the current trunk top of tree, when I open a TCP capture and select Statistics-->IO Graph (for example, happens with other windows) I get a systematic crash.
Here is my build info:

Version 1.7.2 (SVN Rev 42152 from /trunk)

Copyright 1998-2012 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (32-bit) with GTK+ 2.24.10, with Cairo 1.12.0, with Pango 1.29.4, with
GLib 2.32.1, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS
2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built Apr 20 2012), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729


Is anyone having the same issue?

Regards,
Pascal.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe