Bug ID |
10803
|
Summary |
Windows Pipe support broken (development version)
|
Product |
Wireshark
|
Version |
1.99.x (Experimental)
|
Hardware |
x86
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
Capture file support (libwiretap)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 13349 [details]
Error while accessing named pipe via custom interface.
Build Information:
Version 1.99.0 (v1.99.0-2-g9033f13 from master)
Copyright 1998-2014 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 (64-bit) with Qt 5.3.1, with WinPcap (4_1_3), with libz 1.2.5, with
GLib 2.34.1, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, without Kerberos, with GeoIP, without PortAudio,
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), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz (with SSE4.2), with 8073MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 30501
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've been using wireshark from a customized UI using windows pipe.This was
working fine till the last stable release 1.12.2. In the latest development
version When i try to access using a named pipe Timeout error is observed.It
seems the the pipe support is broken or any of the latest updates requires
changes in accessing the pipe ?Attached is the screenshot of the error message.
You are receiving this mail because:
- You are watching all bug changes.