From: Michael Snyder <msnyder@redhat.com>
To: Orjan Friberg <orjan.friberg@axis.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Defer register reading from remote target until needed?
Date: Thu, 03 Jun 2004 18:25:00 -0000 [thread overview]
Message-ID: <40BF6D09.7080909@redhat.com> (raw)
In-Reply-To: <40BF22E2.7030700@axis.com>
Orjan Friberg wrote:
> When single-stepping a remote target, after the stop reply paket is
> sent, GDB immediately sends a request for all registers. Is there a way
> to defer sending this request until some register other than what was
> sent with the stop reply packet (pc, stack and frame pointer) is
> actually needed?
It's supposed to work that way already. Either something's broken, or
some register other than the ones you named *is* needed. The 'g' pkt
should only go out if gdb needs the value of a register that it doesn't
already have.
This can sometimes happen 'indirectly', eg. if you try to set a
register, gdb may try to read it first.
Try setting a breakpoint in remote_fetch_registers, then go up
the stack and see what register gdb is trying to read.
next prev parent reply other threads:[~2004-06-03 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 13:08 Orjan Friberg
2004-06-03 18:25 ` Michael Snyder [this message]
2004-06-04 8:52 ` Orjan Friberg
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=40BF6D09.7080909@redhat.com \
--to=msnyder@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=orjan.friberg@axis.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