When skipping over the padding at the end of a record in a capture file,
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Thu, 2 Sep 1999 00:14:06 +0000 (00:14 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Thu, 2 Sep 1999 00:14:06 +0000 (00:14 +0000)
commit18200bd9fa9ff5cc84e68ff482b9e9020a70b273
tree2c93eb9a0daf955a752110670933867d6d1f342e
parentb835f5ee4361e87697febd42c565974ed0b3388b
When skipping over the padding at the end of a record in a capture file,
don't seek around it - some implementations of the standard I/O library
routines (e.g., the ones in Solaris 2.5.1, at least) appear not to be
clever enough to handle seeks that occur within the buffer by moving the
current buffer position; instead, they do a seek on the underlying file
descriptor *and* appear to throw out the buffer, forcing them to do
another read.

Instead, read it into a buffer.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@626 f5534014-38df-0310-8fa8-9805f1628bb7
wiretap/snoop.c