From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Grzegorz Cieslewski <cieslewski@hcs.ufl.edu>, gdb@sourceware.org
Subject: Re: Setting a floating point register to raw hex value
Date: Thu, 18 Oct 2007 21:54:00 -0000 [thread overview]
Message-ID: <20071018215448.GA12140@caradoc.them.org> (raw)
In-Reply-To: <1192738560.5787.86.camel@localhost.localdomain>
On Thu, Oct 18, 2007 at 06:16:00PM -0200, Thiago Jung Bauermann wrote:
> Hi,
>
> Yes, that's indeed crazy. :-)
>
> Just found out that this works:
>
> (gdb) set (void *) $f1 = 0x1
> (gdb) info reg f1
> f1 4.9406564584124654e-324 (raw 0x0000000000000001)
I think this only works by an accident involving
gdbarch_convert_register_p on PowerPC. We should find some proper way
to do it, document that, and then make this not work :-)
> On Thu, 2007-10-18 at 15:38 -0400, Grzegorz Cieslewski wrote:
> > I have figured out a workaround but it is really ugly.
> >
> > Step 1: Create shared object containing a union as follows
> > union longlong2double
> > {
> > long long int hexNum;
> > double floatNum;
> > } temp;
> >
> > Step 2: Force load the library at runtime into your program using
> > LD_PRELOAD environmental variable
> >
> > Step 3: When debugging the program store 0x1 into temp.hexNum;
> > (one would think that I could use the following now 'set $f0 =
> > temp.floatNum; but that yields incorrect result)
> >
> > Step4: Overwrite the current instruction with 'load float'
> >
> > Step5: Using stepping command 'stepi 1' to write the value to the $f0
> >
> > Step6: Undo all the changes required by steps 4 and 5
> >
> > Does any one know of a simpler way because this workaround is crazy?
Sure, here's a much easier way that ought to work:
(gdb) set {long long} ($sp - 8) = 1
(gdb) set $f0 = {double} ($sp - 8)
Doesn't have to be $sp - 8, any memory address will do.
Oddly, this does not work on PowerPC. I can't figure out why
not. It certainly ought to work; perhaps it requires a current
version of GDB, since 0x1 is a denormal. It does work for normals,
though, so I know the approach is sound.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-18 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 15:29 Grzegorz Cieslewski
2007-10-18 19:38 ` Grzegorz Cieslewski
2007-10-18 20:16 ` Thiago Jung Bauermann
2007-10-18 21:44 ` Grzegorz Cieslewski
2007-10-18 21:54 ` Daniel Jacobowitz [this message]
2007-10-19 19:48 ` Thiago Jung Bauermann
2007-10-19 20:15 ` Daniel Jacobowitz
2007-10-22 16:22 ` Grzegorz Cieslewski
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=20071018215448.GA12140@caradoc.them.org \
--to=drow@false.org \
--cc=bauerman@br.ibm.com \
--cc=cieslewski@hcs.ufl.edu \
--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