From: Teresa Thomas <tthomas@redhat.com>
To: frysk <frysk@sourceware.org>
Subject: Re: minutes of 2007-09-19 meeting
Date: Wed, 19 Sep 2007 15:03:00 -0000 [thread overview]
Message-ID: <46F13A4D.5090408@redhat.com> (raw)
In-Reply-To: <46F13329.6000406@oracle.com>
> Teresa:
> OP_Piece: it's working for registers and memory as far as we know. Not
> turned on yet. Sami reports that testing with that enabled results in
> better test results.
The location code correctly decodes the location of the values, whether
in memory, register or with a memory split. Facing two problems with
manipulating variable values, (1) Getting variable values does not
return expected value in 32 bit machines though it does this for x86_64.
Examining the memory of the task in a 32-bit machine shows that it
contains the LSB of the value at the decoded location, but the the bytes
that follow are random. (2) Frame's setReg does not change the value of
the register. So setting values is possible in memory but not regs.
Its probably not a good idea to enable the new location code atleast
till (1) is fixed.
prev parent reply other threads:[~2007-09-19 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 14:32 Elena Zannoni
2007-09-19 15:03 ` Teresa Thomas [this message]
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=46F13A4D.5090408@redhat.com \
--to=tthomas@redhat.com \
--cc=frysk@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).