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-commits: [Wireshark-commits] rev 19456: /trunk/ /trunk/: capture_loop.c capture_loop.h tshark.c

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


From: ulfl@xxxxxxxxxxxxx
Date: Sun, 08 Oct 2006 22:39:24 GMT

http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=19456

User: ulfl
Date: 2006/10/08 10:39 PM

Log:
 from Richard van der Hoff:
 > [tshark from a fifo]
 > Ulf - I notice you made the relevant change here (r16787) - is there any reason why tshark shouldn't use capture_loop_dispatch to do its processing, rather than attempting to use cap_pipe_dispatch or pcap_dispatch directly?
 
 well, there didn't seem to be, so I've made a patch which does exactly this, and which fixes the problem.

Directory: /trunk/
  Changes    Path              Action
  +5 -5      capture_loop.c    Modified
  +3 -4      capture_loop.h    Modified
  +2 -5      tshark.c          Modified


  • Prev by Date: [Wireshark-commits] rev 19455: /trunk/test/ /trunk/test/: config.sh suite-capture.sh
  • Next by Date: [Wireshark-commits] rev 19457: /trunk/test/ /trunk/test/: config.sh suite-capture.sh
  • Previous by thread: [Wireshark-commits] rev 19455: /trunk/test/ /trunk/test/: config.sh suite-capture.sh
  • Next by thread: [Wireshark-commits] rev 19457: /trunk/test/ /trunk/test/: config.sh suite-capture.sh
  • Index(es):
    • Date
    • Thread

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