Date: Thu, 10 Jun 1999 02:27:30 -0400 (EDT) From: Mike Nowlin <mike@argos.org> To: Phil Homewood <philh@mincom.com> Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: ENABLE_SERIAL_BREAK_KEY...or something? Message-ID: <Pine.LNX.4.05.9906100216360.10213-100000@jason.argos.org> In-Reply-To: <19990610154124.F22693@mincom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > key to drop to the debugger? Say have it so that if a keystroke of ~b (as > > Would be most excellent if this could be done. A couple of boxen I > have here have serial consoles attached to other machines which > do a very good simulation of a break when the controlling process > leaves them. Dropping to DDB every time you reboot the other machine > is, uh, less than desirable behaviour. :-) Agreed, but this may be quite a project... doing a "cd ~bob" would be fun. :) You would pretty much have to implement some timing requirements, but I imagine that it could bulk up that section of the kernel pretty easily. One thing that might help (assuming you CAN generate a break) is to watch DCD (or some other control line(s)). Generally, when a break is sent intentionally, the DCD line is active -- when the kernel detects a break, wait until after it's finished, then check DCD. If it's high, drop to debugger. If it's low, somebody either turned the terminal off or dropped outta kermit. (I have the displeasure of maintaining an AIX box that does something similar to this. Before the upgrade that fixed this problem, turning off the serial console brought the whole machine down.) --Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.05.9906100216360.10213-100000>