Does GNU's C Compiler Have a Full Screen Debugger?

[Richard Michael Todd]

eru at tnvsu1.tele.nokia.fi (Erkki Ruohtula) writes:
>The only CodeView-feature I miss in gdb+emacs is the separate screen for
>program output that prevents program I/O and debugger commands from mixing
>(perhaps the gdb mode could be hacked to use a separate Emacs buffer
>for debugger I/O?).

There's a *really sleazy* way to route the output of your program to a
different window that I've used on occasion.  It works only under X Window,
and is a really cheap hack; no doubt someone can suggest a better way.
Here goes:
   1.	Start up an xterm.  This xterm window will eventually be used for 
the program's output.  When you get a shell prompt, type "tty; sleep 10000"
This will print out the device name (/dev/ttyp?) of the pty for that xterm,
then sleep for hours and hours (meaning you won't have the shell of that 
xterm trying to read from the same tty we'll have our program doing I/O on).
   2.	In another window (either xterm or Emacs), start up gdb on your
program.  Before doing the 'run', issue the command
	tty /dev/ttyp?
where "/dev/ttyp?" is the name of the tty you got in step 1.  Now, all I/O
your program does will be on that tty, hence in that xterm window, and all 
communication with the debugger will be in the original window.  

  Sleazy, but it works....
-- 
Richard Todd   rmtodd at chinet.chi.il.us  or  rmtodd at uokmax.ecn.uoknor.edu  
"MSDOS is a Neanderthal operating system" - Henry Spencer