Message-Id: <m0vhGi1-000S1kC@natacha.inti.edu.ar>
Comments: Authenticated sender is <salvador AT natacha DOT inti DOT edu DOT ar>
From: "Salvador Eduardo Tropea (SET)" <salvador AT natacha DOT inti DOT edu DOT ar>
Organization: INTI
To: Robert Hoehne <robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de>
Date: Mon, 6 Jan 1997 18:20:46 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Question about exceptions
CC: djgpp-workers AT delorie DOT com

Hi All:

> On Mon, 30 Dec 1996, Salvador Eduardo Tropea (SET) wrote:
> 
> > I'm saving the whole 256Kb standard VGA video RAM because you can't 
> > guess about what a hell is doing the debuggee, for example:
> > 
> > 1) Having 2 fonts at the same time (Yes 512 different characters on 
> > screen).
> > 2) Using various pages of text (common).
> > 3) Using a large screen to scroll, for example I use (and I debugged 
> > succesfully) 640x800 with 640x480 visible.
> > 4) In any XMode is totally impossible to know how much memory is 
> > using the program.
> > 5) Tons of things ....
> >  
> As I already wrote, I made the graphic support only for VESA modes
> and VGA 0x12 and 0x13. I think, If a user want to debug some exotic
> graphic modes, he should do it in any othere way because I cannot
> think about any possiblity which can be happen.
Hmmm... is bad, we can support a lot of tricks.

> I think that the best for debugging graphic programs is to debug
> it in standard modes and when it is ready you can use it with
> any special think you want.
  Is totally imposible, you can't test a program that uses an X-mode 
in an standard mode, just imposible.

SET 
--------------- 0 --------------------------------
Salvador Eduardo Tropea (SET).
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013