Date: Wed, 23 Aug 1995 16:42:08 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Steve Higgins <steve>
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: Debugging Graphics Programs.


On Tue, 22 Aug 1995, Steve Higgins wrote:

> Does anyone know of any debugging tools available for debugging graphics
> programs under djgpp114m4? Is the only way to stamp debug info to a file?

Why not try what the FAQ suggests?  It discusses some of the alternatives 
in section 12.7:

12.7  Q: How can I debug a graphics program?  The debugger runs my program
         fine, but when a breakpoint is hit with the screen in a graphics
         mode I can't read the text printed by the debugger.
      A: Redirect the debugger output to another (monochrome) monitor by
         putting ``mono'' into your GO32 environment variable, like this:

            set GO32=mono

         (Note: GDB doesn't support such a redirection yet, but other
         debuggers do.)

         Alternatively, you can redirect the debugger output to your
         printer, like this:

            go32 -d gdb myprog > prn

         You might also consider using the LadyBUG debugger which supports
         remote debugging over a serial link (but it's not source-level).

         As yet another possibility, consider using the MSHELL program
         which will redirect I/O from any program to the monochrome,
         monitor at the BIOS level, so you can use it even with GDB.
         MSHELL was written by DJ Delorie <dj AT delorie DOT com> and is
         available by anonymous ftp to omnigate.clarkson.edu, directory
         pub/msdos/djgpp/pub, file mshell.zip, and also as mshell10.zip
         at ftp.delorie.com:/pub/djgpp/ofc/.

The latest version of the FAQ list should be available as faq102.zip from 
the same place you get DJGPP.