Wireshark-bugs: [Wireshark-bugs] [Bug 8988] GLib-GObject-CRITICAL all the time
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 30 Jul 2013 14:48:39 +0000

Comment # 6 on bug 8988 from 
I don't see that problem on my (GTK3) build:


jmayer@egg:~/work/wireshark/traces> wireshark -v
wireshark 1.11.0 (SVN Rev 51025 from /trunk)

Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> 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+ 3.2.1, with Cairo 1.10.2, with Pango 1.29.4, with
GLib 2.30.1, with libpcap, with libz 1.2.5, with POSIX capabilities (Linux),
with libnl 3, with SMI 0.4.8, with c-ares 1.7.5, with Lua 5.1, without Python,
with GnuTLS 3.0.3, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Oct 29 2011), without AirPcap.

Running on Linux 3.10.1-3.gb92a291-desktop, with locale de_DE.UTF-8, with
libpcap version 1.1.1, with libz 1.2.5, GnuTLS 3.0.3, Gcrypt 1.5.0.

Built using clang 4.2.1 Compatible Clang 3.3 (branches/release_33 183898).


1) Is this specific to some capture file?
2) Can you try to help with finding the place where these messages occur?
   See
http://stackoverflow.com/questions/2450001/how-can-i-find-out-where-is-my-code-causing-glib-gobject-critical

You are receiving this mail because:
  • You are watching all bug changes.