Date: Sun, 20 Jun 2021 10:34:04 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: =?UTF-8?B?W0J1ZyAyNTY3MTJdIFVGUzoga2VybmVsIHBhbmljOiBmZnNfYmxr?= =?UTF-8?B?ZnJlZV9jZzogZnJlZWluZyBmcmVlIGZyYWcg4oCTIGluIHJlc3BvbnNlIHRv?= =?UTF-8?B?IHBrZy1kZWxldGUoOCkgc29vbiBhZnRlciBsb2dpbg==?= Message-ID: <bug-256712-3630-DvvUUjmTTR@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256712-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-256712-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256712 --- Comment #6 from Graham Perrin <grahamperrin@gmail.com> --- (In reply to comment #2) > … Dump Status: good # gdb file /var/crash/vmcore.0 … "/var/crash/vmcore.0" is not a core dump; file format not recognized (gdb) q >From this, I assume that whilst there was true goodness when the status was determined, the file that was then written by savecore(8) became a casualty of file system inconsistency, despite a mark of cleanliness. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256712-3630-DvvUUjmTTR>