Comment # 9
on bug 10803
from julien STAUB
Some information that may be related to this problem :
I tested a minimalist script with "dumpcap -i \\.\pipe\test_pipe" from version
1.12.4 and 1.99 under Windows. Here is the python27 script :
import win32pipe, win32file
p = win32pipe.CreateNamedPipe(r'\\.\pipe\test_pipe',
win32pipe.PIPE_ACCESS_DUPLEX,
win32pipe.PIPE_TYPE_MESSAGE | win32pipe.PIPE_WAIT,
1, 65536, 65536,300,None)
win32pipe.ConnectNamedPipe(p, None)
print "connected to pipe"
data = "" Pipe"
win32file.WriteFile(p, data)
With Wireshark 1.12.4 "connected to pipe" is displayed but not 1.99.
So same problem, it's like the pipe is never opened by Wireshark or dumpcap.
AND
I noticed the dumpcap.exe process never halts when wireshark is closed.
You are receiving this mail because:
- You are watching all bug changes.