Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 8778] New: Wireshark GUI 1.10 crashs within "Capture Interfaces"

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	8778
Summary	Wireshark GUI 1.10 crashs within "Capture Interfaces"
Classification	Unclassified
Product	Wireshark
Version	1.10.0
Hardware	x86-64
OS	Windows 8
Status	UNCONFIRMED
Severity	Major
Priority	Low
Component	Wireshark
Assignee	bugzilla-admin@wireshark.org
Reporter	ferhat.akguen@gmail.com

Build Information:
Version 1.10.0 (SVN Rev 49790 from /trunk-1.10)

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 (64-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Jun  5 2013), with AirPcap.

Running on 64-bit Windows 8, build 9200, with WinPcap version 4.1.3 (packet.dll
version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz, with 6142MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219
--
Hi,

here are the steps to reproduce this crash:

- Start Wireshark 1.10 (64Bit)
- click on Capture menu
- click on Interfaces

In my case here are several devices: (2x VMware, 1x VirtualBox, 2x Ethernet and
1x Wi-Fi).
The crash occurs when clicking on Details button of my Wi-Fi device
(manufacturer = AVM FRITZ!WLAN USB Stick)
This is the only active device!

The GUI is not crashing if I click on the other "Details" buttons .


Unhandled exception at 0x000007F7CD8666AE in Wireshark.exe: 0xC0000005: Access
violation reading location 0x0000000006192044.

I tried to load the symbol files (PDB) in VS to provide you more information
but they do not match with the executables.




My call stack:


>	Wireshark.exe!000007f7cd866b35()	Unknown
     Wireshark.exe!000007f7cd866811()    Unknown
     Wireshark.exe!000007f7cd865d32()    Unknown
     Wireshark.exe!000007f7cd86527f()    Unknown
     Wireshark.exe!000007f7cd864f01()    Unknown
     Wireshark.exe!000007f7cd776848()    Unknown
     libgobject-2.0-0.dll!g_closure_invoke() + 950 bytes    Unknown
     libgobject-2.0-0.dll!g_signal_emit_valist() + 1023 bytes    Unknown
     libgobject-2.0-0.dll!g_signal_emit() + 24 bytes    Unknown
     libgtk-win32-2.0-0.dll!gtk_button_get_alignment() + 933 bytes    Unknown
     libgobject-2.0-0.dll!g_closure_invoke() + 950 bytes    Unknown
     libgobject-2.0-0.dll!g_signal_emit_valist() + 1023 bytes    Unknown
     libgobject-2.0-0.dll!g_signal_emit() + 24 bytes    Unknown
     libgtk-win32-2.0-0.dll!gtk_button_released() + 137 bytes    Unknown
     libgtk-win32-2.0-0.dll!gtk_marshal_VOID__UINT_STRING() + 279 bytes   
Unknown
     libgobject-2.0-0.dll!g_closure_invoke() + 329 bytes    Unknown
     libgobject-2.0-0.dll!g_signal_handler_disconnect() + 2729 bytes    Unknown
     libgobject-2.0-0.dll!g_signal_emit_valist() + 2052 bytes    Unknown
     libgobject-2.0-0.dll!g_signal_emit() + 24 bytes    Unknown
     libgtk-win32-2.0-0.dll!gtk_widget_get_realized() + 557 bytes    Unknown
     libgtk-win32-2.0-0.dll!gtk_propagate_event() + 193 bytes    Unknown
     libgtk-win32-2.0-0.dll!gtk_main_do_event() + 603 bytes    Unknown
     libgdk-win32-2.0-0.dll!gdk_event_get_graphics_expose() + 10027 bytes   
Unknown
     libglib-2.0-0.dll!g_main_context_dispatch() + 278 bytes    Unknown
     libglib-2.0-0.dll!g_main_context_dispatch() + 1064 bytes    Unknown
     libglib-2.0-0.dll!g_main_loop_run() + 115 bytes    Unknown
     libgtk-win32-2.0-0.dll!gtk_main() + 158 bytes    Unknown
     Wireshark.exe!000007f7cd74e817()    Unknown
     Wireshark.exe!000007f7cd75068e()    Unknown
     Wireshark.exe!000007f7cd8d1b93()    Unknown

---

      You are receiving this mail because:

• You are watching all bug changes.