Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Recognize 'x' in response to 'p' packet
Date: Fri, 17 Dec 2004 22:45:00 -0000	[thread overview]
Message-ID: <vt2oegslfis.fsf@zenia.home> (raw)
In-Reply-To: <20041217193240.GA19185@nevyn.them.org>

Daniel Jacobowitz <drow@false.org> writes:
> I know this came up a bit already, but could you elaborate on why you
> had to silently provide a value of 0?  We do have a defined interface
> for 'currently not available', though we do not use it well.  This
> isn't support for the xx response, just a workaround.

I just missed it.  Is this (untested!) what you're looking for?

2004-12-17  Jim Blandy  <jimb@redhat.com>

	* remote.c (fetch_register_using_p): Recognize a register value
	starting with 'x' as indicating an unfetchable register.

Index: gdb/remote.c
===================================================================
RCS file: /cvs/src/src/gdb/remote.c,v
retrieving revision 1.155
diff -c -p -r1.155 remote.c
*** gdb/remote.c	17 Dec 2004 22:19:51 -0000	1.155
--- gdb/remote.c	17 Dec 2004 22:31:09 -0000
*************** fetch_register_using_p (int regnum)
*** 3192,3213 ****
    p += hexnumstr (p, regnum);
    *p++ = '\0';
    remote_send (buf, rs->remote_packet_size);
!   if (buf[0] != 0 && buf[0] != 'E') {
!     p = buf;
!     i = 0;
!     while (p[0] != 0) {
!       if (p[1] == 0) {
!         error("fetch_register_using_p: early buf termination");
!         return 0;
!       }
!       regp[i++] = fromhex (p[0]) * 16 + fromhex (p[1]);
!       p += 2;
      }
-     regcache_raw_supply (current_regcache, regnum, regp);
-     return 1;
-   }
  
!   return 0;
  }
  
  static void
--- 3192,3224 ----
    p += hexnumstr (p, regnum);
    *p++ = '\0';
    remote_send (buf, rs->remote_packet_size);
! 
!   /* If the stub didn't recognize the packet, or if we got an error,
!      tell our caler.  */
!   if (buf[0] == '\0' || buf[0] == 'E')
!     return 0;
! 
!   /* If this register is unfetchable, tell the regcache.  */
!   if (buf[0] == 'x')
!     {
!       regcache_raw_supply (current_regcache, regnum, NULL);
!       set_register_cached (regnum, -1);
      }
  
!   /* Otherwise, parse and supply the value.  */
!   p = buf;
!   i = 0;
!   while (p[0] != 0) {
!     if (p[1] == 0) {
!       error("fetch_register_using_p: early buf termination");
!       return 0;
!     }
! 
!     regp[i++] = fromhex (p[0]) * 16 + fromhex (p[1]);
!     p += 2;
!   }
!   regcache_raw_supply (current_regcache, regnum, regp);
!   return 1;
  }
  
  static void


  reply	other threads:[~2004-12-17 22:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03  0:22 Jim Blandy
2004-12-16 21:35 ` Jim Blandy
2004-12-17 22:20   ` Daniel Jacobowitz
2004-12-17 22:45     ` Jim Blandy [this message]
2004-12-18  1:24       ` Daniel Jacobowitz
2004-12-21 21:30         ` Jim Blandy
2004-12-23 16:43           ` Jim Blandy
2004-12-23 17:22             ` Daniel Jacobowitz
2004-12-28 13:15               ` Jim Blandy
2004-12-03  1:29 Paul Schlie
2004-12-03  4:32 ` Steven Johnson
2004-12-03  4:54   ` Paul Schlie
2004-12-03 13:57     ` Daniel Jacobowitz
2004-12-03 21:48       ` Michael Snyder
2004-12-03 21:45 ` Michael Snyder
2004-12-03 22:53   ` Paul Schlie
2004-12-03 23:44     ` Paul Schlie

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=vt2oegslfis.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=drow@false.org \
    --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