From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: Jerome Guitton <guitton@adacore.com>, Doug Evans <dje@google.com>,
gdb-patches@sourceware.org
Subject: Re: [RFC] setting the raw content of a register
Date: Wed, 23 May 2012 16:22:00 -0000 [thread overview]
Message-ID: <20120523162146.GD5492@adacore.com> (raw)
In-Reply-To: <4FBD0A28.9090503@redhat.com>
My two cents:
One of the concerns I have with the current discussion centering around
using the expression parser is that the syntax would then be language-
sensitive, or might not even be implemented/able in certain languages
at all. I can be a number of scenarios where that becomes a pain
for the user (assuming said user was able to find the right incantation
at all).
Also, I tend to think that the "{TYPE} VAL " expression is a little
obscure to be found easily by someone searching for a way to assign
a raw value to an object. And to widen the discussion, I have always
thought that relying on language expression assignment to change the
value of some variables or even some memory has always been a PIA, and
I would have welcomed a dedicated command to do that.
So, I understand the desire to widen the discussion to find a way
to change the raw value of any object, not just registers, but
I would really prefer in this instance that it did not rely on
pure expression evaluation.
--
Joel
prev parent reply other threads:[~2012-05-23 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 14:37 Jerome Guitton
2012-05-22 14:55 ` Pedro Alves
2012-05-22 15:25 ` Jerome Guitton
2012-05-22 16:32 ` Pedro Alves
2012-05-23 15:22 ` Doug Evans
2012-05-23 15:28 ` Pedro Alves
2012-05-23 15:42 ` Jerome Guitton
2012-05-23 16:03 ` Pedro Alves
2012-05-23 16:10 ` Pedro Alves
2012-05-23 16:22 ` Joel Brobecker [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=20120523162146.GD5492@adacore.com \
--to=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=guitton@adacore.com \
--cc=palves@redhat.com \
/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