On Tue, 9 Nov 1999, Greg Lehey wrote:
> On Tuesday, 9 November 1999 at 8:52:58 -0500, Zhihui Zhang wrote:
> > I have set up an environment of remote serial debugging on FreeBSD
> > 3.3-Release. I have a program that whenever it runs the kernel panics.
> > Is there any way I can use remote serial debugging to trace this panic
> > process instead of examining a dead kernel (i.e., coredump)?
> > Or, is there any way I can use to drop the debugged kernel to debugger
> > mode whenever it runs a certain piece of code?
> Yes. That's what breakpoints are for. If you set a breakpoint on
> panic, you'll go into the debugger. But you don't need that, since
> you go into the debugger on panic anyway.
> If you're expecting a breakpoint or panic, and you want to do it in
> gdb as opposed to ddb, set gdb mode ahead of time. This is also
> useful for debugging ddb :-)
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
How to set gdb mode ahead of time?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message