Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "David Mc Kenna" <mckennad@esatclear.ie>
To: Tim Combs <tcombs@urbana.css.mot.com>,
	David Mc Kenna <mckennad@esatclear.ie>,
	gdb@sources.redhat.com
Subject: Re: Remote Serial Protocol
Date: Wed, 23 Jan 2002 05:56:00 -0000	[thread overview]
Message-ID: <3c4ebc81.47f2.0@esatclear.ie> (raw)

Thanks for the quick reply,

Where are the macros for REGISTER_RAW_SIZE and REGISTER_NAME located ?

Thanks,
Dave McKenna
>The answer used to be in remote.c but now its at the end of the
>documentation:
>read registers g 
>Read general registers. 
>reply XX... 
>Each byte of register data is described by two hex digits. The bytes with 

>the register are transmitted in target byte order. The size of each register

>and their position within the `g' packet are determined by the GDB 
>internal macros REGISTER_RAW_SIZE and REGISTER_NAME macros. 
>
>For instance, if your target had 4 32bit registers (for simplicity) and all
the 
>values were 0xdeadbeef, then the string your target would send back would
>look like:
>deadbeefdeadbeefdeadbeefdeadbeef
>
>(With all the packet info stripped off.)
>
>Tim.Combs@motorola.com
>
>On Wed, Jan 23, 2002 at 01:18:49PM +0000, David Mc Kenna wrote:
>> A question about the Remote Serial Protocol
>> 
>> When gdb issues the command : "+$g#67" , which reads the general registers,

>> what is the format of the expected return.
>> 
>> 
>> Debugging with gdb gives a vague reference but no solid info.
>> 
>> Thanks,
>> Dave Mc Kenna
>> 
>> 
>> 
>> 
>> --
>> http://www.iol.ie
>
>


--
http://www.iol.ie


             reply	other threads:[~2002-01-23 13:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-23  5:56 David Mc Kenna [this message]
2002-01-23  7:36 ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2003-09-05  5:39 remote serial protocol Raja Saleru
2002-01-23  5:37 Remote Serial Protocol David Mc Kenna
2002-01-23  5:48 ` Tim Combs

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=3c4ebc81.47f2.0@esatclear.ie \
    --to=mckennad@esatclear.ie \
    --cc=gdb@sources.redhat.com \
    --cc=tcombs@urbana.css.mot.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