Date: Tue, 9 Nov 1999 13:36:56 -0800 (PST) From: Archie Cobbs <archie@whistle.com> To: zzhang@cs.binghamton.edu (Zhihui Zhang) Cc: grog@lemis.com (Greg Lehey), freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic Message-ID: <199911092136.NAA35735@bubba.whistle.com> In-Reply-To: <Pine.GSO.3.96.991109093952.10214A-100000@sol.cs.binghamton.edu> from Zhihui Zhang at "Nov 9, 1999 09:49:43 am"
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911092136.NAA35735>