| Bug ID |
12143
|
| Summary |
Calling dumpcap -i- results in access violation
|
| Product |
Wireshark
|
| Version |
2.0.1
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Capture file support (libwiretap)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14343 [details]
Patch to fix access violation
Build Information:
dumpcap -v
Dumpcap (Wireshark) 2.0.1 (695041f from master)
Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.8.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, without
WinPcap.
Intel(R) Xeon(R) CPU E31245 @ 3.30GHz (with SSE4.2), with 8148MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 40629
--
Calling dumpcap -i- results in an access violation because
capture_interface_list() is called with a null pointer. The attached patch
fixed it for me.
You are receiving this mail because:
- You are watching all bug changes.
