| Bug ID |
8884
|
| Summary |
Wireshark crashes when switching from a v1.11.0 profile to a v1.4.6 prof and then to a v1.5.1 prof
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.11.x (Experimental)
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Medium
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
| Attachment #11127 Flags |
review_for_checkin?
|
Created attachment 11127 [details]
Same patch submitted under Bug 8865
Build Information:
Version 1.11.0-50214-vanilla (SVN Rev Unknown from unknown)
Copyright 1998-2013 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 (32-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, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Jun 28 2013), with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, 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) Xeon(R) CPU E5507 @ 2.27GHz, with 4093MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
This is likely a duplicate of Bug 3640 and Bug 7722.
I found that it always crashed in the "Capture" preferences module. When i
investigated the capture-related preferences I found some bugs with
capture.columns which I reported in Bug 8865 and supplied a patch. That patch
also prevents Wireshark from crashing when switching between profiles.
I'm resubmitting the patch for Bug 8865 here because that patch has not yet
been checked in. In addition, I'm supplying a different set of profiles than
those submitted in that bug report that specifically demonstrate the crashes.
You are receiving this mail because:
- You are watching all bug changes.
