Date: Tue, 11 Apr 2000 13:06:17 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Dieter Buerssner cc: djgpp-workers AT delorie DOT com Subject: Re: One more GDB for DJGPP little oddity In-Reply-To: <200004101857.UAA26586@is.elta.co.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Mon, 10 Apr 2000, Dieter Buerssner wrote: > > 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). You need to disassemble the code fragment which you are debugging and glean the info from there. > 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. GDB and Bash both use termios, which writes to the console via Int 29h. I have on my (infinite) todo list to add some facility to force termios to use DOS I/O, or change termios to always use DOS I/O when the terminal is in text mode. Volunteers are welcome to work on that ;-) Another idea is to add the dribble functionality to GDB.