Fix a compiler warning.

(Clang FTW!  Is this not an issue on x86-64 macOS, so that it doesn't
warn about it, or does it, unlike GCC, require a particular -W flag to
warn about non-volatile variables being stomped by setjmp/longjmp?)

Change-Id: I253c1ea324feac1372aa4077aaba03c787a47d9f
Reviewed-on: https://code.wireshark.org/review/21248
Reviewed-by: Guy Harris <guy@alum.mit.edu>
This commit is contained in:
Guy Harris 2017-04-20 09:55:35 -07:00
parent 9b0b2c3d59
commit 7312019eac
1 changed files with 1 additions and 1 deletions

View File

@ -643,7 +643,6 @@ main(int argc, char *argv[])
{0, 0, 0, 0 }
};
gboolean arg_error = FALSE;
const char *exp_pdu_filename = NULL;
#ifdef _WIN32
int result;
@ -681,6 +680,7 @@ main(int argc, char *argv[])
int log_flags;
gchar *output_only = NULL;
gchar *volatile pdu_export_arg = NULL;
const char *volatile exp_pdu_filename = NULL;
exp_pdu_t exp_pdu_tap_data;
/*