Message-Id:	<200004101801.OAA29960@delorie.com>
From:	"Dieter Buerssner" <buers AT gmx DOT de>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Date:	Mon, 10 Apr 2000 21:03:16 +0200
MIME-Version:	1.0
Subject:	Re: One more GDB for DJGPP little oddity
CC:	djgpp-workers AT delorie DOT com
References:	<200004101325 DOT JAA17297 AT delorie DOT com>
In-reply-to:	<Pine.SUN.3.91.1000410170213.24866F-100000@is>
X-mailer:	Pegasus Mail for Win32 (v3.12b)
Reply-To:	djgpp-workers AT delorie DOT com

On 10 Apr 00, at 17:09, Eli Zaretskii wrote:

> Sorry, I don't think that's what Pierre was saying (I asked for an 
> example program to be sure I understand).  I think he was saying that 
> when this particular value, 1e+4893 (which cannot be *but* a long 
> double), is loaded into the FPU, "info float" displays Inf instead of its 
> value (which is large, but finite).

Ah. I haven't seen this with info float yet.


> > To debug floating point, you can try to use the compiler option
> > -ffloat-store. 

I forgot to say, that you may need the -ggdb flag, too.

[Problems with this approach]

> Yes.  Therefore, I think that using "info float" is a much better way.  
> You need to get used to the way x87 operates to find where the values 
> are, but that's not very hard.

Yes, info float is useful. But it really can be hard to track down, 
where all the variables are stored, especially when compiling with 
Optimization. (And I think, I do know x87 assembly).

Also, is there a way, to make Gdb print its output to stdout or 
stderr, so that I can use my script utility, to log my debug session?
Right now, it only seems to print its copyright message to the 
stderr/stdout. The other output seems to be written by the BIOS or by 
direct screen access. Not surprisingly, bash has the same problem.

-- 
Regards, Dieter

- Raw text -