Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-bugs: [Wireshark-bugs] [Bug 1759] Trafic from NamedPipes can not be stoped.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sat, 1 Sep 2007 13:45:56 +0000 (GMT)

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.

  • Prev by Date: [Wireshark-bugs] [Bug 1807] BACnet UnconfirmedEventNotification inconsistent decoding
  • Next by Date: [Wireshark-bugs] [Bug 1814] New: Capture filters not work when capturing from named pipes.
  • Previous by thread: [Wireshark-bugs] [Bug 1807] BACnet UnconfirmedEventNotification inconsistent decoding
  • Next by thread: [Wireshark-bugs] [Bug 1814] New: Capture filters not work when capturing from named pipes.
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation