Date: Thu, 22 Oct 1998 15:24:10 -0400 From: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com> To: "Bill Fenner" <fenner@parc.xerox.com>, "Brett Glass" <brett@lariat.org> Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>, "shmit@kublai.com" <shmit@kublai.com>, "Studded" <Studded@gorean.org> Subject: Re: No terminal echo after certain commands Message-ID: <199810221925.PAA19893@laker.net>
next in thread | raw e-mail | index | archive | help
On Thu, 22 Oct 1998 11:59:54 PDT, Bill Fenner wrote: >In message <4.1.19981021161615.00be3ef0@mail.lariat.org> you write: >>Suggestions on how to attack this? It looks as if the code really is not >>operating as intended. > >Run "more" in one window, and run "gdb more <pid>" in another. That >way your gdb window doesn't have to get mangled by the terminal futzing >that "more" does. A recent post indicated that this aberrant behavior does not exist in the latest versions. I can't remember if they said 3.0R and stable, or current?? You may want to check the archives and find out which versions appear to not have the problem so you can try out your testcase. Could save you from wasting your time fixing something that's already done... Of course, it's also a great academic exercise... Unix systems measure "uptime" in years, Winblows measures it in minutes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810221925.PAA19893>