http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=32986
User: guy
Date: 2010/05/26 05:48 PM
Log:
Clean up the error reporting. An EOF from the sync pipe when capturing
is just an indication that the capture child exited; don't treat it as
an error, unless the child process exits with an abnormal status.
As tshark sends a "stop capture" indication to the child when it's
^C'ed, the child will exit and we'll get an EOF from the capture pipe;
don't make SIGINT etc. interrupt system calls, so they don't cause reads
from the capture pipe to get EINTR errors.
Directory: /trunk/
Changes Path Action
+115 -72 capture_sync.c Modified
+20 -8 tshark.c Modified
