From owner-freebsd-hackers Tue Nov 9 14:35: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 2D3EF14C41 for ; Tue, 9 Nov 1999 14:34:48 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id OAA27935; Tue, 9 Nov 1999 14:34:36 -0800 (PST) Date: Tue, 9 Nov 1999 14:34:35 -0800 (PST) From: Julian Elischer To: Archie Cobbs Cc: Zhihui Zhang , Greg Lehey , freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic In-Reply-To: <199911092136.NAA35735@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG uh archie, that's a whistle specific sysctl :-) On Tue, 9 Nov 1999, Archie Cobbs wrote: > Zhihui Zhang writes: > > Thanks for your reply. What confuses me is that when I use commands "gdb" > > (enter remote protocol mode) and "step" on the target machine, the > > debugging machine takes control (it executes "target remote /dev/cuaa1"). > > In this case, how can I run anything on the target machine to trigger a > > panic? > > I'm not sure if this answers your question, but the command > > sysctl -w debug.cebugger=1 > > will cause the kernel to stop and return your gdb prompt. > Then you could call the function panic() directly if you wanted. > > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message