From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: Jason Molenda <jmolenda@apple.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: [remote protocol] step range?
Date: Mon, 08 Sep 2008 04:56:00 -0000 [thread overview]
Message-ID: <20080908045522.GA3766@caradoc.them.org> (raw)
In-Reply-To: <48C32177.6060507@vmware.com>
On Sat, Sep 06, 2008 at 05:33:59PM -0700, Michael Snyder wrote:
> Well you know, guys, it's always optional for a target
> to implement a new protocol command. If there's a target
> for which this would be hard, or wouldn't gain you much,
> you can always leave it un-implemented.
Yes, I'm more concerned about e.g. inlining. Basically, anything in
the inferior control loop that would be surprised by more than one
step.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-09-08 4:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 22:15 Michael Snyder
2008-09-05 0:12 ` Jason Molenda
2008-09-05 2:39 ` Michael Snyder
2008-09-06 0:17 ` Jason Molenda
2008-09-06 1:09 ` Michael Snyder
2008-09-06 4:16 ` Daniel Jacobowitz
2008-09-07 0:35 ` Michael Snyder
2008-09-08 4:56 ` Daniel Jacobowitz [this message]
2008-09-05 2:32 ` Daniel Jacobowitz
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=20080908045522.GA3766@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jmolenda@apple.com \
--cc=msnyder@vmware.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