On 19 September 2014 18:03, Pascal Quantin <pascal.quan...@gmail.com> wrote:
> > Le 16 sept. 2014 08:25, "Anders Broman" <a.broma...@gmail.com> a écrit : > > > > > > Den 16 sep 2014 08:00 skrev "Pascal Quantin" <pascal.quan...@gmail.com>: > > > > > > > > > > > Le 15 sept. 2014 23:13, "Gerald Combs" <ger...@wireshark.org> 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. > Yet another nail in the GTK coffin? We'll just all have to try a bit harder to bring the QT build up to speed. Note it's now "The QT Company", Digia have taken a step back. See http://blog.qt.digia.com/blog/2014/09/16/the-qt-company-introduces-a-unified-website-and-20e25-monthly-indie-mobile-package/ -- Graham Bloice
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
