Path: utzoo!attcan!uunet!lll-winken!ames!pasteur!ucbvax!bloom-beacon!mit-eddie!uw-beaver!rice!sun-spots-request
From: richard%aiai.edinburgh.ac.uk@nss.cs.ucl.ac.uk (Richard Tobin)
Newsgroups: comp.sys.sun
Subject: Re: Bad interaction between dbxtool and tcsh
Message-ID: <6605.8901191236@subnode.aiai.ed.ac.uk>
Date: 26 Jan 89 07:31:11 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 27
Approved: Sun-Spots@rice.edu
Original-Date: Thu, 19 Jan 89 12:36:18 GMT
X-Sun-Spots-Digest: Volume 7, Issue 122, message 4 of 11

[problem: dbxtool from tcsh doesn't echo]

It's probably in cbreak mode as well.  A common problem with programs that
include some kind of terminal emulator is that they decide what modes to
run their pseudo-terminal in by looking at the modes of their own control
terminal.  (A good idea in principle, since it allows them to get your
suspend/eof/erase characters right.)

Various shells run in no-echo and cbreak modes so that they can do
interesting line editing.  They set the modes back before running a
program in the foreground, but not before running one in the background.
Thus I conclude that you are running dbxtool in the background.

Possible solutions:

(1) Run it in the foreground.  This ties up your shelltool.
(2) Start it in the foreground, suspend it and put it in the background,
    Unfortunately dbxtool appears to ignore SIGTSTP so you'll have to do
    "kill -STOP pid" from another window.
(3) Start it from the background menu.  Then you have to cd to the right
    directory and say 'debug program'.
(4) Type "dbxtool & sleep 2", or something similar.  The idea is that tcsh
    will be waiting for sleep (with the terminal modes normal) when dbxtool
    looks at the modes.  This isn't guaranteed to work, because the timing
    is not reliable.

-- Richard