From owner-freebsd-current Sat Mar 29 13:53:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA15514 for current-outgoing; Sat, 29 Mar 1997 13:53:29 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA15508; Sat, 29 Mar 1997 13:53:26 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id NAA00536; Sat, 29 Mar 1997 13:53:25 -0800 (PST) Message-Id: <199703292153.NAA00536@austin.polstra.com> To: Mike Pritchard cc: current@freefall.freebsd.org Subject: Re: Panic: "lockmgr: pid %d, not %s %d unlocking" In-reply-to: Your message of "Sat, 29 Mar 1997 13:17:05 PST." <199703292117.NAA13611@freefall.freebsd.org> References: <199703292117.NAA13611@freefall.freebsd.org> Date: Sat, 29 Mar 1997 13:53:25 -0800 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > How come the panic message wasn't expanded? The original panic message that came out on the console was expanded. The output I included in my posting came from running "gdb -k" later, on the kernel + crash dump. I guess it's not expanded at that point. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth