Wireshark-bugs: [Wireshark-bugs] [Bug 2888] New: Typing "Start" for eth0 in the Interfaces dialo
Date: Sat, 20 Sep 2008 10:33:39 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2888

           Summary: Typing "Start" for eth0 in the Interfaces dialog causes
                    Wireshark to hang / freeze
           Product: Wireshark
           Version: 1.0.3
          Platform: PC
        OS/Version: Linux (other)
            Status: NEW
          Severity: Critical
          Priority: Medium
         Component: Wireshark
        AssignedTo: [email protected]
        ReportedBy: [email protected]


Build Information:
Version 1.0.3

Copyright 1998-2008 Gerald Combs <[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 with GTK+ 2.14.2, with GLib 2.18.1, with libpcap 0.9.8, with libz
1.2.3, with POSIX capabilities (Linux), with libpcre 7.8, without SMI, without
ADNS, without Lua, with GnuTLS 2.4.1, with Gcrypt 1.4.1, with MIT Kerberos,
without PortAudio, without AirPcap.

Running on Linux 2.6.27-desktop-0.rc6.3.2mnb, with libpcap version 0.9.8.

Built using gcc 4.3.2.

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
I'm starting wireshark as root from a binary I compiled from source on Mandriva
Linux Cooker.

Capture -> Interfaces -> eth0 -> Start causes Wireshark to hang / freeze / get
stuck / become unresponsive. 

<<<<<<<<<<
gdb says the following:

#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb595eadb in wait () from /lib/i686/libpthread.so.0
#2  0x0806e1a0 in sync_pipe_close_command (read_fd=0xae601060, msg=0xbfd0dfac)
    at capture_sync.c:755
#3  0x0806e69a in sync_interface_stats_close (read_fd=0xae601060,
    fork_child=0xae601064, msg=0xbfd0dfac) at capture_sync.c:990
#4  0x0806bae8 in capture_stat_stop (sc=0xae601060) at capture.c:865
#5  0x080c79c9 in capture_if_destroy_cb (win=0x94bad10, user_data=0xae601060)
    at capture_if_dlg.c:295
#6  0xb5c7fee0 in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#7  0xb5c722f8 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#8  0xb5c88e88 in ?? () from /usr/lib/libgobject-2.0.so.0
#9  0xb5c8a569 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#10 0xb5c8a9b7 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#11 0xb60e5071 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#12 0xb61e7f31 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#13 0xb61f5ba6 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#14 0xb5c749f7 in g_object_run_dispose () from /usr/lib/libgobject-2.0.so.0
#15 0xb60e4d6e in gtk_object_destroy () from /usr/lib/libgtk-x11-2.0.so.0
#16 0x08086646 in window_destroy (win=0x94bad10) at gui_utils.c:550
#17 0x080c762e in capture_do_cb (capture_bt=0x94e62f0, if_data=0xae600db0)
>>>>>>>>>>>


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.