Wireshark-dev: Re: [Wireshark-dev] Systematic crash at startup when launching Wireshark GTK+ 1.
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Pascal Quantin <pascal.quantin@xxxxxxxxx>
Date: Fri, 19 Sep 2014 19:03:25 +0200


Le 16 sept. 2014 08:25, "Anders Broman" <a.broman58@xxxxxxxxx> a écrit :
>
>
> Den 16 sep 2014 08:00 skrev "Pascal Quantin" <pascal.quantin@xxxxxxxxx>:
>
> >
> >
> > Le 15 sept. 2014 23:13, "Gerald Combs" <gerald@xxxxxxxxxxxxx> a écrit :
> >
> > >
> > > On 9/15/14 10:51 AM, Gerald Combs wrote:
> > > > On 9/15/14 10:02 AM, Pascal Quantin wrote:
> > > >>
> > > >> It explains why it works fine with 1.12.0 then... And why I could not
> > > >> figure out a major difference in main.c file explaining the behavior
> > > >> while using the same libraries!
> > > >
> > > > If I build a package from g0a24908 (the commit prior to the GTK+ package
> > > > upgrade) Wireshark-gtk.exe starts up OK.
> > >
> > > I created a GTK+ bundle using the current OBS packages (GTK+ 2.24.23 +
> > > GLib 2.40.0) but Wireshark-gtk still crashes on Windows 8. We might have
> > > to revert back to the GTK+ 2.14 bundle or to Visual C++ 2010 in master.
> >
> > If we have no other choice I would prefer downgrading the GTK+ package as it will become obsolete with time. And I would not have to reinstall a MSVC2010 build environment... But I'm probably selfish ;)
>
> Upgrading to this package solved a severe memory leak with windows server and RDP, I think.
> Not sure what the best of two evils are...

Especially as Digia only provide x64 Qt libraries compiled against MSVC2013... So it looks like we cannot win on both sides.
>
> >
> >
> > ___________________________________________________________________________
> > 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
>
>
> ___________________________________________________________________________
> 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