🚀 go-pugleaf

In Reply to this Note From: <Bob Sutterfield>
>
>In article <54@bmhalh.UUCP> bruce@bmhalh.UUCP (Bruce M. Himebaugh) writes:
>   Does the GNU C compiler have a full screen debugger available?
>
[text deleted]
>   If so, is it anything like codeview?
>
>Sorry, I don't know anything about codeview.
>

I have used CodeView, and am stumping now for GDB to work more like it.
CodeView has two modes, one with multiple windows while the program
is dormant, and one with the program output while it is running.
It switches rapidly from one screen to the other as you step through 
the program.  Perhaps GDB could only display the output window when
text is actually being displayed.  The use of separate windows as
done now is just as good or better.

What I really like about CodeView is the display and form of interaction.
The code of the program being debugged is visible in a window (hence
its name), and the line being executed is always visible and highlighted
unless you specify otherwise.  The display returns to the current line
whenever you step through a line of code.

A window can be used to view the values of variables AS THEY CHANGE.
Breakpoints can be set for various conditions, including for when
a C expression becomes true.

The biggest drawback to CodeView is that it has multiple operating
venues.  One might argue that this is good, because different people
prefer different styles, but I have found that not all functions
are available in every venue, forcing me to mix venues.

For example, a function is available as a Function Key, as an 
item in a pull-down menu, and as a shell command.  I would
prefer that everything was a shell command, with the ability
to define keys as macros.  This may be possible in CodeView,
but I have not learned how to do it.  The pull-down menus are 
nice, but inefficient once you are past the learning phase.

I have used dbx, but not gdb.  The main advantage of CodeView is
its namesake, that you can see the state of the execution visually
at any time.  The use of function keys for major functions, like
"Step One Line" make it easy to see things happen.

CodeView is the debugger provided with MicroSoft language products.
-David-

david@wubios.wustl.edu             ^     Mr. David J. Camp
david%wubios@wugate.wustl.edu    < * >   +1 314 382 0584
...!uunet!wugate!wubios!david      v     "God loves material things."