By default, don't stop after a read error.

For close to 10 years, we have defaulted not to stop processing on an
open error; default not to stop processing on a read error, either.  -C
causes us to stop for both.

Bug: 15433
Change-Id: I5cd239c160d0ff85eb0425ca4b172532a4659fd3
Reviewed-on: https://code.wireshark.org/review/31710
Reviewed-by: Guy Harris <guy@alum.mit.edu>

1 files changed, 8 insertions, 7 deletions

diff --git a/capinfos.c b/capinfos.c
index afab0dbac4..72fb14a6a5 100644
--- a/capinfos.c
+++ b/capinfos.c
@@ -88,14 +88,14 @@
 /*
  * By default capinfos now continues processing
  * the next filename if and when wiretap detects
- * a problem opening a file.
+ * a problem opening or reading a file.
  * Use the '-C' option to revert back to original
  * capinfos behavior which is to abort any
- * additional file processing at first open file
- * failure.
+ * additional file processing at the first file
+ * open or read failure.
  */
 
-static gboolean stop_after_wtap_open_offline_failure = FALSE;
+static gboolean stop_after_failure = FALSE;
 
 /*
  * table report variables
@@ -1561,7 +1561,7 @@ main(int argc, char *argv[])
         break;
 
       case 'C':
-        stop_after_wtap_open_offline_failure = TRUE;
+        stop_after_failure = TRUE;
         break;
 
       case 'A':
@@ -1679,7 +1679,7 @@ main(int argc, char *argv[])
     if (!wth) {
       cfile_open_failure_message("capinfos", argv[opt], err, err_info);
       overall_error_status = 2; /* remember that an error has occurred */
-      if (stop_after_wtap_open_offline_failure)
+      if (stop_after_failure)
         goto exit;
     }
 
@@ -1691,7 +1691,8 @@ main(int argc, char *argv[])
       wtap_close(wth);
       if (status) {
         overall_error_status = status;
-        goto exit;
+        if (stop_after_failure)
+          goto exit;
       }
     }
   }