we can even get error messages while we are capturing (e.g. when a network cable...

problem found by Joerg Mayer

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

diff --git a/capture.c b/capture.c
index 6bb18ca01f29a4d32f5715e2a6966d6b9783a08c..4cfb3fc4b7aaaff6f75d7c62823e0451238ee1cb 100644 (file)
--- a/capture.c
+++ b/capture.c
@@ -359,17 +359,17 @@ capture_input_drops(capture_options *capture_opts, int dropped)
 }
 
 
-/* Capture child told us, that an error has occurred while starting the capture. */
+/* Capture child told us, that an error has occurred while starting/running the capture. */
 void
 capture_input_error_message(capture_options *capture_opts, char *error_message)
 {
   g_log(LOG_DOMAIN_CAPTURE, G_LOG_LEVEL_MESSAGE, "Error message from child: \"%s\"", error_message);
 
-  g_assert(capture_opts->state == CAPTURE_PREPARING);
+  g_assert(capture_opts->state == CAPTURE_PREPARING || capture_opts->state == CAPTURE_RUNNING);
 
   simple_dialog(ESD_TYPE_ERROR, ESD_BTN_OK, "%s", error_message);
 
-  /* the capture child will close the sync_pipe, nothing to do for now */
+  /* the capture child will close the sync_pipe if required, nothing to do for now */
 }