Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!beta!hc!ames!elroy!devvax!perez
From: perez@devvax.JPL.NASA.GOV (Craig D. Perez)
Newsgroups: comp.lsi,comp.unix.questions
Subject: Re: Help needed when using DBX and MAGIC
Message-ID: <604@devvax.JPL.NASA.GOV>
Date: Fri, 23-Oct-87 12:45:31 EST
Article-I.D.: devvax.604
Posted: Fri Oct 23 12:45:31 1987
Date-Received: Sun, 25-Oct-87 16:12:19 EST
References: <7671@steinmetz.steinmetz.UUCP> <217@PT.CS.CMU.EDU>
Reply-To: perez@devvax.JPL.NASA.GOV (Craig D. Perez)
Organization: Jet Propulsion Laboratory, Pasadena, CA.
Lines: 16
Keywords: dbx MAGIC sun
Xref: mnetor comp.lsi:268 comp.unix.questions:4642

In article <217@PT.CS.CMU.EDU> gwu@VLSI.CS.CMU.EDU (George Wu) writes:
>
>     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. Playing with the tty status (via reset) only confuses the issue more.

   I have never had trouble with dbx and cbreak mode... dbx runs my
program normally when I am debugging. The only reason why I could see
I/O problems with dbx is if MAGIC is doing non standard reads and
writes in cbreak mode (i.e. playing directly with screen attributes
and terminal settings).
                              Craig (Perez@devvax.JPL.NASA.Gov)

DISCLAIMER: I'm myself and no one else... This is MY opinion!!!
-----------> Please direct flames to me and not the net...