Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <dje@google.com>, <tromey@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [RFC] Don't allow setting register in non-innermost frame
Date: Fri, 07 Sep 2012 13:14:00 -0000	[thread overview]
Message-ID: <5049F2D6.1040807@codesourcery.com> (raw)
In-Reply-To: <83r4qeax91.fsf@gnu.org>

On 09/07/2012 07:27 PM, Eli Zaretskii wrote:
>> >How about them below?
>> >
>> >* GDB will display a warning when assigning to registers, for example
>> >    "set $eax=0x1", in non-innermost frames.
>> >
>> >or
>> >
>> >* GDB will display a warning when assigning to registers by command
>> >    "set" in non-innermost frames.
> If "set" is the only command, then the second variant is better.  But
> isn't the same true of the MI equivalent?

It is true to the MI command "-var-assign".  How about this?

* GDB will display a warning when assigning to registers by CLI command
   "set" or MI command "-var-assign" in non-innermost frames.

-- 
Yao


  reply	other threads:[~2012-09-07 13:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17  2:21 Yao Qi
2012-08-20 20:19 ` Doug Evans
2012-08-21  3:27   ` Yao Qi
2012-08-23 16:25   ` Tom Tromey
2012-08-29  9:51     ` Yao Qi
2012-09-04 22:37       ` dje
2012-09-07 10:01         ` Yao Qi
2012-09-07 10:11           ` Eli Zaretskii
2012-09-07 10:21             ` Yao Qi
2012-09-07 11:27               ` Eli Zaretskii
2012-09-07 13:14                 ` Yao Qi [this message]
2012-09-07 14:32                   ` Eli Zaretskii
2012-09-07 16:46     ` Jan Kratochvil
2012-09-09  2:31       ` Yao Qi
2012-09-10  2:02       ` Yao Qi
2012-09-10  7:47         ` Jan Kratochvil
2012-09-10 19:43           ` Jan Kratochvil
2012-09-11 17:12         ` Tom Tromey
2012-09-11 17:19           ` Jan Kratochvil
2012-09-11 17:23             ` Tom Tromey
2012-09-12  0:51           ` Yao Qi
2012-09-12 13:19             ` Jan Kratochvil

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=5049F2D6.1040807@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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