Make the "go" member of the "loop_data" structure in Ethereal a
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Thu, 3 Jan 2002 22:03:24 +0000 (22:03 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Thu, 3 Jan 2002 22:03:24 +0000 (22:03 +0000)
commit267dadbfaac56803865b8bb7b113920d7e496a0d
tree04392a3df5637d3f8de4eb62c3270de49013dc5f
parentae56f3550cd4d86606ac51aca616795a723b4312
Make the "go" member of the "loop_data" structure in Ethereal a
"gboolean", as it's a Boolean value, and move it to the beginning of the
structure in Tethereal, as it is in Ethereal.

From Graeme Hewson:

Check for "pcap_dispatch()" returning -1, meaning an error
occurred; if it does, stop capturing, and report the error.

If we get a signal in tethereal, stop the capture with a
"longjmp()", rather than by clearning the "go" flag;
"pcap_dispatch()", on many platforms, keeps reading rather than
returning a captured packet count of 0 if the system call to
read packets returns -1 with an errno of EINTR, so the
"pcap_dispatch()" won't be broken out of if the signal handler
returns.

Fix a typo in an error message.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@4471 f5534014-38df-0310-8fa8-9805f1628bb7
AUTHORS
capture.c
tethereal.c