Date: Sun, 10 Mar 2002 21:46:48 -0800 (PST) From: Julian Elischer <julian@elischer.org> To: Glenn Gombert <ggombert@imatowns.com> Cc: Robert Watson <rwatson@FreeBSD.org>, current@FreeBSD.org Subject: Re: Serial break into debugger broken from 'cu' on -CURRENT? Message-ID: <Pine.BSF.4.21.0203102145070.61447-100000@InterJet.elischer.org> In-Reply-To: <3.0.6.32.20020310150813.00daf458@imatowns.com>
next in thread | previous in thread | raw e-mail | index | archive | help
serial break is different.. it is suppoesed to break into the d debugger if it receives a "BREAK" (i.e framing error) in the serial port. cu ,tip and other such programs have an escape sequence to "send a break" julian On Sun, 10 Mar 2002, Glenn Gombert wrote: > I just rebuilt -current on two development machines I use here at home, the > serial break "contol-alt-escape" appears to work fine on a stand-alone vox. > > > >(1) Is serial break currently broken in -CURRENT > > If I do a 'tip com1' from one box to the other and then do an > 'control-alt-escape' it breaks into ddd just fine as well : > > >(2) Is serial break currently broken in 'cu'? > > > > Glenn Gombert > ggombert@imatowns.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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?Pine.BSF.4.21.0203102145070.61447-100000>