Xref: utzoo comp.unix.sysv386:1734 gnu.misc.discuss:1930 comp.lang.c:33331 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!unisoft!hoptoad!kumr!pozar From: pozar@kumr.UUCP (Tim Pozar) Newsgroups: comp.unix.sysv386,gnu.misc.discuss,comp.lang.c Subject: Re: Does GNU's C Compiler Have a Full Screen Debugger? Message-ID: <233@kumr.UUCP> Date: 31 Oct 90 17:36:43 GMT References: <54@bmhalh.UUCP> <1990Oct29.230734.1871@sctc.com> Reply-To: pozar@kumr.UUCP (Tim Pozar) Organization: Late Night Software (San Francisco) Lines: 24 In article <1990Oct29.230734.1871@sctc.com> stachour@sctc.com (Paul Stachour) writes: > Do you mean the codeview debugger available on MS-DOS with Microsoft-C? > If so, than I would not call that a full-screen debugger because: > > #1: It requires two physical screens to do the debugging, one-to-run > and one-to-debug. Are you saying CodeView needs two different monitors? If so, I have found this to be untrue. With a keystroke, I can move back and forth between the 'debugging' screen with the source, registers, and varibles displayed and, the "programme output" screen (text or graphics). I think what is meant by "Full screen debugger" is that there is a method to display the code, registers, ect and not destroy the programme's screen at the same time while stepping through the code. Old debuggers would use the same screen, therefore destroying what the programme is painting on the screen. Tim -- uunet!hoptoad!kumr!pozar Fido: 1:125/555 PaBell: (415) 788-3904 USNail: KKSF-FM / 77 Maiden Lane / San Francisco CA 94108