https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16192
--- Comment #1 from Chuck Craft ---
Created attachment 17455
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17455&action=edit
tshark -r and capinfos - success and errors
For each pcapng in the zip, output of tshark -r and cap
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16192
Dario Lombardo changed:
What|Removed |Added
CC||lom...@gmail.com
Sta
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16192
João Valverde changed:
What|Removed |Added
CC||joao.valverde@tecnico.ulisb
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16192
Guy Harris changed:
What|Removed |Added
OS|Windows 10 |All
Hardware|x86
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16192
Guy Harris changed:
What|Removed |Added
Hardware|ARM |All
--
You are receiving this mail
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16192
--- Comment #5 from Guy Harris ---
Perhaps if tshark is writing to the standard output, and it gets EPIPE, it
should just silently exit rather than reporting the EPIPE as a write error.
For Windows, we should try to figure out *why* it's
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16192
Guy Harris changed:
What|Removed |Added
Status|INCOMPLETE |CONFIRMED
--
You are receiving this
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16192
--- Comment #6 from Guy Harris ---
(In reply to João Valverde from comment #3)
> > For what I can see the output is correct: head is cutting the input short
> > and that's why tshark complains. But the output is correct. Can you
> > elabor
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16192
--- Comment #7 from Chuck Craft ---
Googling around for Broken Pipe is quite the can of worms.
Not sure that I could foresee all cases where it's just ok to discard.
What would be nice is if something like "-Q" could be extended to suppres
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16192
--- Comment #8 from Guy Harris ---
(In reply to Chuck Craft from comment #7)
> Googling around for Broken Pipe is quite the can of worms.
> Not sure that I could foresee all cases where it's just ok to discard.
One place is in show_print_
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16192
--- Comment #9 from Gerrit Code Review ---
Change 35053 had a related patch set uploaded by Guy Harris:
Don't report EPIPE errors writing out packet information.
https://code.wireshark.org/review/35053
--
You are receiving this mail bec
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16192
--- Comment #10 from Gerrit Code Review ---
Change 35054 had a related patch set uploaded by Guy Harris:
Don't report EPIPE errors writing out packet information.
https://code.wireshark.org/review/35054
--
You are receiving this mail be
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16192
--- Comment #11 from Gerrit Code Review ---
Change 35055 had a related patch set uploaded by Guy Harris:
Don't report EPIPE errors writing out packet information.
https://code.wireshark.org/review/35055
--
You are receiving this mail be
13 matches
Mail list logo
