On Tuesday, 9 November 1999 at 13:36:56 -0800, 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.
Take a look at /usr/src/sys/modules/vinum/.gdbinit.kernel. There's
some almost undocumented stuff in there, including a macro called
ddb. Call it from gdb and it'll switch back to ddb.
Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
