Date: Mon, 14 Jun 1999 10:25:01 +0300 (WET)
From: Andris Pavenis <pavenis AT ieva01 DOT lanet DOT lv>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: djgpp-workers AT delorie DOT com
Subject: Re: save_npx and FSDB/Edebug32
In-Reply-To: <Pine.SUN.3.91.990613112114.17906Q-100000@is>
Message-ID: <Pine.A41.4.05.9906141020200.24354-100000@ieva01.lanet.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk



On Sun, 13 Jun 1999, Eli Zaretskii wrote:

> Did someone try to build and use one of the above with the v2.03 version 
> of dbgcom.c?
> 
> I think the new feature of saving and restoring the FPU state as part of
> run_child will break the FP support in these debuggers, since FNSAVE does
> an equivalent of FNINIT after saving the FPU state. 
> 

I know about this feature of FNSAVE. 

Most my own applications use floating point. At least my own experience
with debuggers shows that FP supports works there. However I think that
having 2 FPU states (one for debugger, second for debugee) which are 
swapped before and after running child (as suggested in one of earlier
posts to this mailing list) would be better.  

Andris