On Tuesday, 18 May 1999 at 9:17:03 +0200, Sheldon Hearn wrote: > > On Tue, 18 May 1999 16:34:55 +0930, 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. > > This is something new since about 4 months ago, then? I used 0x10 on a > 4.0-CURRENT machine a while back and managed to do remote debugging > successfully (after a little help from you, in fact). :-)
On Tuesday, 18 May 1999 at 9:09:34 +0100, Doug Rabson 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. Kirk committed some stuff a week or two ago. And yes, IIRC it was to allow the same serial port to be used for both purposes. Greg -- See complete headers for address, home page and phone numbers finger [email protected] for PGP public key To Unsubscribe: send mail to [email protected] with "unsubscribe freebsd-hackers" in the body of the message
