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: "Graham Bloice" <graham.bloice@xxxxxxxxxxxxx>
Date: Fri, 20 Apr 2012 14:06:45 +0100

FWIW I am compiling with VC Express 2010 on XP, all 32 bit.

 

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Graham Bloice
Sent: 20 April 2012 13:36
To: 'Developer support list for Wireshark'
Subject: Re: [Wireshark-dev] Crash with the new win32 GTK+ bundle when opening an analysis window

 

I see it as well after a distclean and manually removing some left behind detritus so I’m pretty certain everything was rebuilt.

 

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman
Sent: 20 April 2012 13:30
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Crash with the new win32 GTK+ bundle when opening an analysis window

 

Hi,

Did you try a clean build of top-of-tree?

Regards

Anders

 

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Pascal Quantin
Sent: den 20 april 2012 14:00
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Crash with the new win32 GTK+ bundle when opening an analysis window

Hi Evan,

2012/4/20 Evan Huus <eapache@xxxxxxxxx>

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.


Thanks for the suggestion. Reverting revision 42150 (your change to conversation.c) did not help.  Instead reverting revision 42143 (Gerald's change so as to use the new GTK+ package) solves the crash for me.

Regards,
Pascal.