From: Michael Snyder <msnyder@vmware.com>
To: Michael Snyder <msnyder@vmware.com>,
Pedro Alves <pedro@codesourcery.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
teawater <teawater@gmail.com>
Subject: Re: [RFA] Reverse Debugging, 2/5
Date: Mon, 06 Oct 2008 21:38:00 -0000 [thread overview]
Message-ID: <48EA84C6.9080803@vmware.com> (raw)
In-Reply-To: <20081006212405.GA31085@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Mon, Oct 06, 2008 at 02:10:18PM -0700, Michael Snyder wrote:
>> Pedro Alves wrote:
>>> On Wednesday 01 October 2008 20:17:54, Michael Snyder wrote:
>>>> + /* TODO: check target for capability. */
>>> Can we address this? If you want to be able to query for support,
>>> it would be a matter of defining a new qSupported feature.
>> OK -- but what about existing targets that support reverse,
>> but don't know about the qSupported query?
>>
>> When I put that comment in, I probably intended an implied
>> question-mark -- that is, I wasn't asserting that a query
>> would be useful, just wondering aloud...
>
> All qSupported probes can be overridden by a manual setting. I don't
> feel particularly bad about forcing people to update, if there's a
> workaround - that's part of getting protocol changes merged :-)
I see. So we would just make them type "set reverse-supported on"
or something like that.
> However, I'm not completely sure it's necessary in this case. When do
> we check for capability? If it's only at the appropriate run/continue
> command, then probing is OK - though this would make it hard to,
> e.g., automatically enable IDE buttons.
Well, MI isn't in there yet, though I've heard from a
possible contributor. How about if we put qSupported
into a later patch as well?
Nothing wrong with the present target implementers being
supported in the first version...
>> Yeah, I hear ya -- I'm not crazy about it either, and I
>> don't think I knew about the idea of adding new tags onto
>> the "T" packet two years ago.
>>
>> But... the discussion about the remote protocol for this
>> happened back in '06. There are now targets out in the field
>> that implement it this way. It would be bad form to break them...
>
> I'm pretty sure nothing about this error was in that discussion. At
> least, I think I would have objected at the time.
You're probably right. But it was certainly in my earlier
patch submissions.
prev parent reply other threads:[~2008-10-06 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 19:19 Michael Snyder
2008-10-06 19:50 ` Pedro Alves
2008-10-06 21:12 ` Michael Snyder
2008-10-06 21:24 ` Daniel Jacobowitz
2008-10-06 21:38 ` Michael Snyder [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=48EA84C6.9080803@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=teawater@gmail.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