🚀 go-pugleaf

In article <1993May5.170548.1@woods.ulowell.edu> mcardleb@woods.ulowell.edu writes:
>HI,
>	I was trying to use the djgcc debugger for my 486 PC (DOS)
>and would like to know if I am using it right.  I don't have ansi.sys
>and the environment variable (I forget which) knows that.  When I start

All ansi.sys does is let you have nifty colors for each section.

>the debugger with my a.out I get some colored information at the top
>of the screen then  it disappears and I am using a line debugger.  I know

Those numbers are the current EIP and memory (and vm if used) left.

>that it only shows the assembly but I though there would be window with 
>the assembly and a cursor pointing at the execution point so I could

No scrolling, but you can set breakpoints.

>maybe scroll around and set breakpoints set easily.  Is this really a 
>line debugger with a bad interface?

Yup.  

>GCC is a great project and a good debugger environment would make it SUPREME!

You've got the source, go to it!!  Hard part is, all the debugger brains
are in real memory, so not much memory to play around with when wanting to
make a nifty neato interface.  Best bet is to use two monitors, and debug from
the mono monitor.

regards,
mrc
-- 
Mike Castle .-=NEXUS=-.  Life is like a clock:  You can work constantly
  mcastle@cs.umr.edu     and be right all the time, or not work at all
S087891@UMRVMA.UMR.EDU   and be right at least twice a day.  -- mrc
    We are all of us living in the shadow of Manhattan.  -- Watchmen