Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [wanted] Test of GDB modifying a value in a register
Date: Mon, 04 Nov 2002 16:00:00 -0000	[thread overview]
Message-ID: <3DC70A0F.CB818723@redhat.com> (raw)
In-Reply-To: <3DC31374.5060902@redhat.com>

Andrew Cagney wrote:
> 
> Hello,
> 
> In doing a further cleanup of the frame code, I discovered that the
> current testsuite isn't testing the codepaths that write a value in a
> register.
> 
> That is, things like:
> 
> (gdb) set $pc = 10
> register int i;
> (gdb) set i = 10;
> 
> Anyone interested in comming up with, or have a test case?


Well, $pc is the only one I can think of that we can count on
being defined on all targets -- and based on some past conversations
with you, I'm wondering if even that is a safe assumption?

Basically, we have almost no tests of register functionality, 
and yes it would be good if we did.


  reply	other threads:[~2002-11-05  0:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01 15:51 Andrew Cagney
2002-11-04 16:00 ` Michael Snyder [this message]
2002-11-04 16:25   ` Andrew Cagney

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=3DC70A0F.CB818723@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.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