Date: Fri, 21 May 1999 08:44:18 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: dfr@nlsystems.com Cc: alpha@freebsd.org Subject: Re: Debugging Message-ID: <199905211544.IAA43739@vashon.polstra.com> In-Reply-To: <Pine.BSF.4.05.9905180908070.509-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <Pine.BSF.4.05.9905180908070.509-100000@herring.nlsystems.com>, Doug Rabson <dfr@nlsystems.com> wrote: > On Tue, 18 May 1999, Greg Lehey wrote: > > > In fact, there's also a 0x80, which you need to set (along with 0x10, > > it appears) to run remote debugging. I'm guessing a bit at this, > > since I haven't had time to look at the code, but 0x90 works for me. > > Doug? > > I used to use 0x50 but now 0x80 works fine. I'm not sure why the debug > flag changed from 0x40 to 0x80 but the new systems seems to allow both > serial console and serial debugging at the same time so I'm not > complaining. There must be something I'm missing here. On i386 systems I have always used one serial port for both console and remote gdb, since the dawn of time. Why the sudden need for a new flag? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905211544.IAA43739>