Handle the 2GiB boundary case of the max filesize autostop condition properly so...
authorcmaynard <cmaynard@f5534014-38df-0310-8fa8-9805f1628bb7>
Thu, 29 Aug 2013 18:15:13 +0000 (18:15 +0000)
committercmaynard <cmaynard@f5534014-38df-0310-8fa8-9805f1628bb7>
Thu, 29 Aug 2013 18:15:13 +0000 (18:15 +0000)
commitdd5f69b2052ad5b6faf6d2838a260f591c188a55
treefc06b8170f66f0422810abf5eae8cbcaf3119703
parent9a3e993ed6c5115aabdf6f2eba4f62a2428feb23
Handle the 2GiB boundary case of the max filesize autostop condition properly so that we avoid overflow conditions and so that we ensure we don't capture more than 2GiB.  Also, document the max filesize autostop value of 2GIB as well as indicating that it's truly GiB and not GB.

This fixes the problem reported on ask: http://ask.wireshark.org/questions/23891/wireshark-wont-run-with-multiple-capture-files

#BACKPORT(1.10) ... not sure about 1.8?

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@51576 f5534014-38df-0310-8fa8-9805f1628bb7
capture_opts.c
capture_opts.h
capture_stop_conditions.c
capture_sync.c
doc/dumpcap.pod
doc/tshark.pod
doc/wireshark.pod.template
dumpcap.c
ui/gtk/capture_dlg.c