Date: Tue, 9 Nov 1999 14:34:35 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: Archie Cobbs <archie@whistle.com> Cc: Zhihui Zhang <zzhang@cs.binghamton.edu>, Greg Lehey <grog@lemis.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic Message-ID: <Pine.BSF.4.10.9911091434110.14483-100000@current1.whistle.com> In-Reply-To: <199911092136.NAA35735@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9911091434110.14483-100000>