Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!amdahl!oliveb!sun!gorodish!guy
From: guy%gorodish@Sun.COM (Guy Harris)
Newsgroups: comp.unix.questions
Subject: Re: Help needed when using DBX and MAGIC
Message-ID: <31864@sun.uucp>
Date: Fri, 23-Oct-87 17:07:34 EST
Article-I.D.: sun.31864
Posted: Fri Oct 23 17:07:34 1987
Date-Received: Sun, 25-Oct-87 18:36:02 EST
References: <7671@steinmetz.steinmetz.UUCP> <217@PT.CS.CMU.EDU>
Sender: news@sun.uucp
Lines: 19
Keywords: dbx MAGIC sun

>      I would guess that the reason for this lies somewhere along the lines
> that Magic tries to do I/O in cbreak mode. Dbx on the other hand wants to use
> the normal buffered I/O mode. So of course, a conflict occurs, and dbx gives
> up.

Nope.  "dbx", at least on Suns (and I suspect on most, if not all, other
machines), has no problem with programs using "cbreak" mode; it will restore
the tty modes before prompting for input, if necessary.  (It doesn't quite
handle *output* modes as smoothly - it resets them *after* it's printed a bunch
of stuff.)

The problem, as was mentioned elsewhere, is that processes being traced with
"ptrace" stop when they receive *any* signal.  "dbx" can be told that if the
process stops with any of a particular set of signals, it should immediately
continue the process; SIGIO is not in the default set of "continue immediately"
signals, but can be added to that set with "ignore IO".
	Guy Harris
	{ihnp4, decvax, seismo, decwrl, ...}!sun!guy
	guy@sun.com