Date: Mon, 18 May 1998 09:53:20 +0930 From: Greg Lehey <grog@lemis.com> To: Bruce Evans <bde@zeta.org.au>, pst@juniper.net, regnauld@deepo.prosa.dk Cc: current@FreeBSD.ORG, julian@whistle.com, scrappy@hub.org Subject: Re: Serial console, system hangs and DDB... Message-ID: <19980518095320.E427@freebie.lemis.com> In-Reply-To: <199805171744.DAA08122@godzilla.zeta.org.au>; from Bruce Evans on Mon, May 18, 1998 at 03:44:36AM %2B1000 References: <199805171744.DAA08122@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 May 1998 at 3:44:36 +1000, Bruce Evans wrote: >> There already is such a thing -- it's called "BREAK_TO_DEBUGGER". >> >> You need to send a <break> indication down the serial line to the target >> machine. The ~# that you're probably sending to your solaris machines >> is actually getting translated by tip(1) into a break signal. > > It is fairly broken, however. It only works if interrupts are enabled > on the serial port for the console, and interrupts are only enabled if > a process (e.g., getty or a shell) has the console open. This makes > it useless for debugging bootstraps, reboots, and serial ports with > broken interrupts. How do you get gdb to send a break? Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980518095320.E427>