Debugging printouts, to see why tshark -G crashes on the Win64 buildbot.

Change-Id: I16f6b7a69eed5ec66842df9d0640216fd273d3b0
Reviewed-on: https://code.wireshark.org/review/17408
Reviewed-by: Guy Harris <guy@alum.mit.edu>
This commit is contained in:
Guy Harris 2016-08-30 19:23:09 -07:00
parent 290e23299d
commit 33bb9bed3e
1 changed files with 8 additions and 0 deletions

View File

@ -829,11 +829,18 @@ main(int argc, char *argv[])
XXX - we do this here, for now, to support "-G" with no arguments.
If none of our build or other processes uses "-G" with no arguments,
we can just process it with the other arguments. */
fprintf(stderr, "Checking for -G\n");
if (argc >= 2 && strcmp(argv[1], "-G") == 0) {
fprintf(stderr, "-G detected\n");
proto_initialize_all_prefixes();
fprintf(stderr, "proto_initialize_all_prefixes() returned\n");
if (argc == 2)
{
fprintf(stderr, "calling proto_registrar_dump_fields()\n");
proto_registrar_dump_fields();
fprintf(stderr, "proto_registrar_dump_fields() returned\n");
}
else {
if (strcmp(argv[2], "column-formats") == 0)
column_dump_column_formats();
@ -878,6 +885,7 @@ main(int argc, char *argv[])
return 1;
}
}
fprintf(stderr, "About to return\n");
return 0;
}