The option --zero_excluded can be used to analyze the incomplete dumpfile. So it is needed to remind users of using it when trying to analyze incomplete dumpfile without --zero_excluded. -- Thanks Zhou Wenjian
--- main.ori 2015-07-21 15:22:57.122000237 +0800 +++ main.c 2015-07-21 15:56:18.360999472 +0800 @@ -709,12 +709,18 @@ "unpredictable\n runtime behavior.\n", pc->dumpfile); - if (pc->flags2 & INCOMPLETE_DUMP) + if (pc->flags2 & INCOMPLETE_DUMP) { error(WARNING, "\n%s:\n " "This dumpfile is incomplete. This may cause the crash session" "\n to fail entirely, may cause commands to fail, or may" " result in\n unpredictable runtime behavior.\n", pc->dumpfile); + if (!(*diskdump_flags & ZERO_EXCLUDED)) + error(WARNING, + "The incomplete dumpfile can be analyzed with" + " --zero_excluded\n and the lost part" + " will be regarded as data filled zero.\n"); + } if (!(pc->flags & GDB_INIT)) { gdb_session_init();
-- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility