🚀 go-pugleaf

	   I can reproduce this problem on both Ultrix and SunOS.

   Description:

	   If I invoke emacs from one of my xterm windows, dbx no longer works
   correctly. By this I mean that once the emacs has been invoked, dbx never
   works for the rest of the lifetime of the window...even if the emacs is
   terminated. I am using version 18.52.25

   More Detail:

	   When I say dbx doesn't work correctly, I mean that it gives the
   following error when the program being debugged is waiting for input and
   you try to give it input:

    On Sun4:


       (dbx) run
       Running: io

       signal IO (possible input/output) in read at 0xf799a98c
       0xf799a98c:     ta      %g0
       (dbx)

    On Ultrix:

       (dbx) run


       I/O possible in read at 0xba0
       00000ba0  bcs   b94
       (dbx)

	   The program runs fine outside of dbx regardless of whether I have
   run a emacs or not.

	Any ideas?

-josh simons (simons@think.com)