http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1759
------- Comment #2 from mmh@xxxxxxxxxxxxx 2007-09-01 13:45 GMT -------
I just want to clarify the problem.
When we capture from 1 named pipe on Windows, the stop button does not act
until the next received packet.
This means that if there is no new packet to be received from pipe, we can not
stop the capture.
I think this is due to using blocking function to read from pipe.
Maybe read from pipe must be done in a separate thread.
--
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.