From: Thomas Baruchel <baruchel@gmx.com>
To: gdb@sourceware.org
Subject: Dump values from FPU after each operation
Date: Fri, 04 Nov 2011 08:15:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1111040907470.13796@lili-Inspiron-1525> (raw)
Hi, I have a compiled program with no debugging symbol (and no source if
you want to ask). I would like to know how some floating point value is
made of, and since I know what value I am looking for, I think one easy
way would be to lauch the program and to have on the standard output the
content of the FPU after each operation; I am aware it will be a huge
amount of value, but since I know which value is expected, I could
probably parse this output to grep (with -A / -B options in order to extract
100 lines around the exact matching). But is it possible to do such a thing?
I am aware that dumping these registers will not tell me the operations,
but this is not a big issue; I can probably guess it once I know the
involved floating-point values.
If the data can't be redirect to standard output, I can save it, this is not
the most important. Regards,
--
Thomas Baruchel
next reply other threads:[~2011-11-04 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 8:15 Thomas Baruchel [this message]
2011-11-04 9:18 ` Eli Zaretskii
2011-11-04 16:46 ` Thomas Baruchel
2011-11-04 17:34 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1111040907470.13796@lili-Inspiron-1525 \
--to=baruchel@gmx.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).