Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9533] Piping dumpcap to tshark results not stable

Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 9533] Piping dumpcap to tshark results not stable

From: bugzilla-daemon@xxxxxxxxxxxxx

Date: Mon, 09 Dec 2013 23:57:47 +0000

Jakub Zawadzki changed bug 9533

What	Removed	Added
Attachment #12277 Flags		review_for_checkin-

Comment # 2 on bug 9533 from Jakub Zawadzki

Created attachment 12277 [details]
Skip bytes with read() if lseek() failed with ESPIPE.

Hello,

can you test attached patch?

Anyway this is also pcapng reader bug, it should check if file_seek() returns
-1 (and report good error).

You are receiving this mail because:

You are watching all bug changes.

References:
- [Wireshark-bugs] [Bug 9533] New: Piping dumpcap to tshark results not stable
  - From: bugzilla-daemon

Prev by Date: [Wireshark-bugs] [Bug 9009] Support for SSH captures (tcpdump/dumpcap)
Next by Date: [Wireshark-bugs] [Bug 9535] New: Buildbot crash output: fuzz-2013-12-09-15167.pcap
Previous by thread: [Wireshark-bugs] [Bug 9533] Piping dumpcap to tshark results not stable
Next by thread: [Wireshark-bugs] [Bug 9534] New: tshark/dumpcap doesn't clean up ringbuffer files when it has fallen behind
Index(es):
- Date
- Thread

© Wireshark Foundation · Privacy Policy

Facebook·Mastodon·Twitter·YouTube