Date: Wed, 11 Sep 2002 13:15:53 -0700 (PDT) From: Nate Lawson <nate@root.org> To: John Polstra <jdp@polstra.com> Cc: hackers@freebsd.org Subject: Re: interrupting target kernel using single sio Message-ID: <Pine.BSF.4.21.0209111315170.22261-100000@root.org> In-Reply-To: <200209091530.g89FUZF4028832@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 9 Sep 2002, John Polstra wrote: > In article <20020909112248.A613@gicco.cablecom.ch>, > Hanspeter Roth <freebsd-hackers@FreeBSD.ORG> wrote: > > > > using a single serial cable I can pass control to the remote kgdb > > pressing ctl-alt-del at the target host. > > I'm looking for a means to interrupt the target kernel from the > > remote host. > > I got suggestions using a second serial cable or using ipgdb > > instead. > > Setting remotechat didn't help me. > > > > Is it intended to be able to interrupt the target kernel from the > > remote kgdb by some means at all? Or is this a wrong expectation? > > BSD/OS has a little state machine in its sio driver which notices > if something looking like a kgdb packet comes in and interrupts > the target automatically. It's extremely handy. You just type > "target remote /dev/tty00" into kgdb and the target breaks into the > debugger -- no muss, no fuss. I wish we had this feature too. It > should obviously be under the control of a sysctl to protect against > accidental entry into the debugger. > > Another nice thing about BSD/OS is that when you exit kgdb, the target > OS automatically starts running again. So you can enter and exit the > debugger painlessly, as many times as you'd like. Any chance of getting that from BSD/OS? If not, perhaps we could reimplement. -Nate 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.21.0209111315170.22261-100000>