Wireshark-bugs: [Wireshark-bugs] [Bug 2087] New: Recent Windows Buildbot versions crash when Cap
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2087
Summary: Recent Windows Buildbot versions crash when Capture
Interface is changed
Product: Wireshark
Version: SVN
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Major
Priority: Medium
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: jyoung@xxxxxxx
Build Information:
Version 0.99.8-SVN-23808 (SVN Rev 23808)
Copyright 1998-2007 Gerald Combs <gerald@xxxxxxxxxxxxx> 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.12.3, with GLib 2.14.4, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with SMI 0.4.5, with ADNS, with Lua 5.1,
with
GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio PortAudio
V19-devel, with AirPcap.
Running on Windows XP Service Pack 1, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Recent Windows Buildbot versions of Wireshark consistently crash if I open the
"Wireshark: Capture Options" dialog and click on the "Interface:" field (as if
I was going to change my default NIC) and then either click on the "Start" of
"Cancel" buttons.
This problem exists with the most recent Windows Buildbot version SVN Rev
23808.
Using other Buildbot versions that I have, I've now replicated these same
symptoms using an older Buildbot version SVN Rev 23681. I could not reproduce
this problem using an even older Buildbot version SVN Rev 23611.
So it looks like something changed between SVN 23611 and 23681 that introduced
this particular problem. Perhaps the more recent changes made between SVN
23611 and 23681 simply made an existing bug finally rear its ugly head. :-(
With Windows Buildbot version SVN Rev 23808 when Wireshark crashes Microsoft's
error dialog pop-ups and reports: "Wireshark has encountered a problem and
needs to close. We are sorry for the inconvenience." By pressing on the
"click here" the following "Error signature" is consistently reported:
> AppName: wireshark.exe AppVer: 0.99.8.0 ModName: msvcrt.dll
> ModVer: 7.0.2600.1106 Offset: 00033830
I can successfully use the "Wireshark: Capture Interfaces" dialog to start a
capture using any of my NICs. Once I've started a capture using the
"Wireshark: Capture Interfaces" dialog, Wireshark will not crash if I open the
Wireshark: Capture Options" dialog (which now lists the recently used NIC as
the selected NIC.
But I don't think the problem is strictly related to selecting the "Interface:"
field of the "Wireshark: Capture Options" dialog. Sometimes when I start
capturing with my default NIC, a strange small area of the screen will remain
corrupted as if Wireshark had started to create another Window. This
corrupted region of the screen remains on top. The appearance of this garbage
window seems to occur when the "Wireshark: Capture from <MY NIC>" window is
enabled. The garbage window persist even after I stop the capture. When this
garbage window appears I will usually be able to stop and save the captured
data. But Wireshark will crash when I go to exit. When Wireshark
closes/crashes the garbage window also disappears.
Obviously this appears to be some type of memory corruption.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
