From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: stop reply packets in rsp
Date: Fri, 13 Jun 2003 23:09:00 -0000 [thread overview]
Message-ID: <20030613230911.GA27969@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0306131559330.29534@knuth.amplepower.com>
On Fri, Jun 13, 2003 at 04:07:53PM -0700, Theodore A. Roth wrote:
> Hi,
>
> The rsp documentation for the 'T' stop reply packet seems a bit
> sparse. Is there a minimal set of registers that must be passed to
> avoid gdb sending a 'g' request while stepping? I assume this is arch
> specific. For the avr it looks like SP and PC are the minimal set.
>
> Does gdb have any preferance as to which reply packets it would like
> to see? My remote targets seem to do ok with using 'T' replies for
> 'C', 'c', 'S', and 's' command packets and 'S' replies otherwise.
In general, if you can supply a 'T', do; then make the tradeoff
(bandwidth vs latency) to supply as many registers as are reasonably
useful. Sometimes GDB fetches more registers, f.ex. to determine
function arguments in the frame.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-06-13 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 23:03 Theodore A. Roth
2003-06-13 23:09 ` Daniel Jacobowitz [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=20030613230911.GA27969@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@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