Xref: utzoo comp.unix.sysv386:1728 comp.lang.c:33326 gnu.misc.discuss:1928 Path: utzoo!telly!attcan!uunet!nih-csl!lhc!mimsy!haven!udel!wuarchive!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!dd26+ From: dd26+@andrew.cmu.edu (Douglas F. DeJulio) Newsgroups: comp.unix.sysv386,comp.lang.c,gnu.misc.discuss Subject: Re: Does GNU's C Compiler Have a Full Screen Debugger? Message-ID: <0b=h49S00VI8MFOhY=@andrew.cmu.edu> Date: 31 Oct 90 13:26:33 GMT References: <54@bmhalh.UUCP> , <1990Oct31.031227.20715@uokmax.ecn.uoknor.edu> Distribution: gnu Organization: Chemistry, Carnegie Mellon, Pittsburgh, PA Lines: 19 In-Reply-To: <1990Oct31.031227.20715@uokmax.ecn.uoknor.edu> eru@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?). rmtodd@uokmax.ecn.uoknor.edu (Richard Michael Todd) writes: > 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... Why do you say that your method works only under X? Start up an emacs shell session (M-x shell) and you can do the same thing in there. It's still "sleazy", but it gets the desired effect of using three emacs buffers -- one with source code, one with a debugger, and one with program output. This way it will work on a normal terminal. Not everyone can stomach the idea of running X11. -- Doug DeJulio