www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1995/02/13/11:26:02

Date: Thu, 9 Feb 1995 15:09:38 -0500 (EST)
From: Kimberley Burchett <OKRA AT max DOT tiac DOT net>
Subject: mono monitors
To: DJGPP Mailing List <djgpp AT sun DOT soe DOT clarkson DOT edu>

  Yesterday I got a mono monitor so I could debug my programs, most of
which run in graphics modes.  It works, but I can't get djgpp working with
it. 
  This is what I can do.  If I use 'topline' and 'mono', I get the 
topline on the mono monitor.  If I do '1rm', I get most everything on the 
monitor.  So obviously the monitor _works_.
  This is what I can't do.  I can't get gdb to use the mono for the
regular interactive debugging stuff (examining source, data, etc) unless I
use '1rm', in which case I get _everything_ on the mono - even the output 
from the program.  This might be the expected behavior, but it isn't what 
I expected.
  Also I thought it would be nice to be able report errors from within the
program on the mono while the color screen is in graphics mode so I used
'2rm'.  This works fine unless I use make.  Make reports the errors it
finds in my sources on the mono, but as soon as it's done with a file, it
clears the mono screen, erasing all the reported errors.
  Also, apparently go32 thinks the top of the mono monitor is about six
lines down.  It scrolls fine, but it always starts about six rows down.  
That isn't too annoying, but I thought it might give a clue as to why 
things aren't working.
							Kim


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019