Xref: utzoo comp.unix.sysv386:1687 gnu.misc.discuss:1920 comp.lang.c:33291 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!agate!linus!nixbur!nixpbe!unido!mcsun!sunic!news.funet.fi!funic!santra!mjolner!newshost!eru From: eru@tnvsu1.tele.nokia.fi (Erkki Ruohtula) Newsgroups: comp.unix.sysv386,gnu.misc.discuss,comp.lang.c Subject: Re: Does GNU's C Compiler Have a Full Screen Debugger? Message-ID: Date: 30 Oct 90 15:26:40 GMT References: <54@bmhalh.UUCP> Sender: news@mjolner.tele.nokia.fi Distribution: gnu Organization: Nokia Telecommunications Lines: 27 In-reply-to: pinard@IRO.UMontreal.CA's message of 27 Oct 90 16:26:47 GMT In article pinard@IRO.UMontreal.CA (Francois Pinard) writes: In article <54@bmhalh.UUCP> bruce@bmhalh.UUCP (Bruce M. Himebaugh) writes: Does the GNU C compiler have a full screen debugger available? If so, is it anything like codeview? To my knowledge, gdb is not full screen in the same sense CodeView is. However, GNU Emacs may to run gdb as a subprocess (the M-x gdb ... Even if some might argue on this, to a certain extent, I consider this is full screen debugging. I agree. I have used both CodeView and gdb+emacs, and I like the latter combination better. For instance, the ability to start directly editing what you see in the source window (using the same editor you use normally), does not exist in CodeView. 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?). -- Erkki Ruohtula / Nokia Telecommunications eru@tele.nokia.fi / P.O. Box 33 SF-02601 Espoo, Finland Disclaimer: These are my private opinions and do not represent the position of Nokia Telecommunications.