From: Paul Koning <pkoning@equallogic.com>
To: drow@false.org
Cc: gdb@sourceware.org
Subject: Re: [remote] Checking for supported packets
Date: Wed, 22 Mar 2006 16:39:00 -0000 [thread overview]
Message-ID: <17440.3444.354136.447113@gargle.gargle.HOWL> (raw)
In-Reply-To: <20060321051221.GA15578@nevyn.them.org>
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Daniel> On Mon, Mar 13, 2006 at 09:15:26PM -0500, Daniel Jacobowitz
Daniel> wrote:
>> I've been working, for the last couple of months, on a wide
>> variety of projects that involve new remote protocol packets. I'm
>> planning to submit each and every one of them; I've just been
>> busy, and also some of them aren't quite fully baked yet.
Daniel> ...
>> Something like this:
>>
-> qPackets?
>> <- qPackets,qPacketSize+,qOffsets-,qPart:available+,qC-
>>
>> "I support the qPacketSize and qPart:available queries, but don't
>> bother probing for qOffsets or qC, they won't work".
Daniel> Don't suppose anyone had time to look at this?
Not to speak of, unfortunately...
Daniel> I don't know if there's any active GDB maintainers, right
Daniel> now, who are interested in the remote protocol. Or e.g. stub
Daniel> developers who are interested, and reading this list. As I
Daniel> said, I have a whole bundle of upcoming proposed additions to
Daniel> the remote protocol; I do my best to design them
Daniel> intelligently and compatibly, and I will document them
Daniel> prettily and post them for review, but the benefit's much
Daniel> lessened if there's no one interested in reviewing them :-)
We're every day users of the remote protocol, and I've done some minor
digging into it. So I'm interested.
I've certainly noticed that the sensing of stub capabilities right now
is rather messy and chatty. The specific example I ran into was the
support of hardware watchpoints and/or breakpoints.
paul
next prev parent reply other threads:[~2006-03-21 14:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 2:15 Daniel Jacobowitz
2006-03-21 14:28 ` Daniel Jacobowitz
2006-03-22 16:39 ` Paul Koning [this message]
2006-03-31 6:38 ` [PROPOSAL] " Daniel Jacobowitz
2006-03-31 9:51 ` Eli Zaretskii
2006-03-31 14:09 ` Daniel Jacobowitz
[not found] ` <uvetuaep4.fsf@gnu.org>
[not found] ` <20060331141958.GA28073@nevyn.them.org>
2006-04-01 10:22 ` Eli Zaretskii
2006-05-10 7:21 ` [PROPOSAL] Checking for supported packets - revised Daniel Jacobowitz
2006-05-10 18:44 ` Eli Zaretskii
2006-05-10 21:49 ` Daniel Jacobowitz
2006-05-11 6:02 ` Eli Zaretskii
2006-05-11 0:19 ` Jim Blandy
2006-05-11 2:26 ` Daniel Jacobowitz
2006-05-11 2:36 ` Jim Blandy
2006-05-12 13:55 ` Daniel Jacobowitz
2006-05-12 18:24 ` PAUL GILLIAM
2006-05-23 22:11 ` Data for: " Daniel Jacobowitz
2006-05-26 22:12 ` Take three: [PROPOSAL] Checking for supported packets 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=17440.3444.354136.447113@gargle.gargle.HOWL \
--to=pkoning@equallogic.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).