Date: Sun, 22 Dec 1996 09:15:08 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Salvador Eduardo Tropea (SET)" <salvador AT natacha DOT inti DOT edu DOT ar>
cc: Robert Hoehne <robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de>,
        djgpp-workers AT delorie DOT com
Subject: Re: Question about exceptions
In-Reply-To: <m0vaiQn-000S1kC@natacha.inti.edu.ar>
Message-ID: <Pine.SUN.3.91.961222090615.29376G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Thu, 19 Dec 1996, Salvador Eduardo Tropea (SET) wrote:

> There another problem: What happends if the debugee uses your own 
> descriptor for the screen? you can't avoid that easily.

This consideration is valid, but not necessarily a fatal problem.  I could
argue that a debugger doesn't need to support any trick a programmer can
devise.  If people want to get debugging support, they could try a little
harder and not use techniques which make debugging hard.  Alternatively,
if they cannot do things in a compatible way, they will have to live
without automatic display switching. 

FYI, there already are quite a few things which don't work in a debugged 
program (like signals).  Is it so bad to tell people that if they use one 
of the incompatible techniques, they will have to manually press a key 
which switches between debugger and user display?  I don't think so.

And FWIW, I find the automatic switching in the Turbo Debugger to be more
of a nuisance than a feature.  The cases where it wedged my machine far
outnumber the advantage of not having to press Alt-F5.  So I usually 
disable it.