Hi, Putting Reply-ASAP in the Subject row is not realy useful :-( I suspect this is related to http://wiki.wireshark.org/Development/Roadmap
Rev 38045<http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=38045>, Rev 38046<http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=38046> - Bug 6540<https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6540> - Don't use g_mutex without having threads. If try applying thos two patches. Using a more modern GTK than GTK+ 2.10.4, with GLib 2.12.3 may also help. Best regards Anders ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Krishnamurthy Mayya Sent: den 14 november 2011 06:39 To: Developer support list for Wireshark Subject: [Wireshark-dev] Reply-ASAP Hi all, Even though i have been able to compile the code successfully, when trying to run wireshark ( ./wireshark ) I am getting the following errors. How should i fix this. GLib-ERROR **: The thread system is not yet initialized. aborting... Trace/breakpoint trap The build information is mentioned below: wireshark 1.6.3 (SVN Rev 39702 from /trunk-1.6) Copyright 1998-2011 Gerald Combs <[email protected]<mailto:[email protected]>> 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.10.4, with GLib 2.12.3, with libpcap 0.9.4, with libz 1.2.3, without POSIX capabilities, without libpcre, without SMI, without c-ares, without ADNS, without Lua, without Python, with GnuTLS 1.4.1, with Gcrypt 1.4.4, without Kerberos, without GeoIP, without PortAudio, without AirPcap. NOTE: this build doesn't support the "matches" operator for Wireshark filter syntax. Running on Linux 2.6.27.21-ZebOS782, with libpcap version 0.9.4, with libz 1.2.3, GnuTLS 1.4.1, Gcrypt 1.4.4. Built using gcc 4.1.2 20080704 (Red Hat 4.1.2-51). Thanks and regards Krishnamurthy Mayya
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
