From: Andrew Cagney <ac131313@cygnus.com>
To: Quality Quorum <qqi@theworld.com>
Cc: "Sarnath K - CTD, Chennai." <k_sarnath@ctd.hcltech.com>,
gdb@sources.redhat.com
Subject: Re: Thread Support for remote debugging
Date: Mon, 21 Jan 2002 08:38:00 -0000 [thread overview]
Message-ID: <3C4C43F4.70005@cygnus.com> (raw)
In-Reply-To: <Pine.SGI.4.40.0201211006021.9204384-100000@shell01.TheWorld.com>
>
>
> I put together spec and reference implementation, see section
> on Remote GDB Protocol at http://world.std.com/~qqi, it is
> 4.18 based though.
>
> I would like also to draw maintainer's attention to this
> work - it fixes quite a few problems existing in the mainline.
>
> If there is a public interest I can integrate it with
> recent stuff.
It fell of the end of my queue :-( You'll notice I've started trying to
restructure the remote doco, restructuring/working on the protocol spec
comes under. From memory you've also got an assignment in place.
BTW, at the risk of sounding pedantic. Can you please change your page
to clarify that gdb.texinfo and remote.c together define the remote
protocol. You've posted a really good draft formal specification.
Andrew
next prev parent reply other threads:[~2002-01-21 16:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 1:11 Sarnath K - CTD, Chennai.
2002-01-21 6:07 ` Daniel Jacobowitz
2002-01-21 7:10 ` Quality Quorum
2002-01-21 8:38 ` Andrew Cagney [this message]
2002-01-31 12:47 ` Michael Snyder
2002-01-31 15:12 ` Daniel Jacobowitz
2002-01-31 15:22 ` Quality Quorum
2002-01-31 17:22 ` Daniel Jacobowitz
2002-01-31 19:41 ` Quality Quorum
2002-01-31 19:29 ` Andrew Cagney
2002-01-31 19:44 ` Quality Quorum
2002-01-31 15:41 ` Michael Snyder
2002-01-31 17:18 ` Daniel Jacobowitz
2002-01-31 17:21 ` Michael Snyder
2002-01-21 22:08 Sarnath K - CTD, Chennai.
2002-01-31 23:32 Korbel, Michal
2002-02-01 7:45 ` Dan Kegel
2002-02-01 8:13 Korbel, Michal
2002-02-01 8:27 ` Dan Kegel
2002-02-01 9:43 ` Quality Quorum
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=3C4C43F4.70005@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=k_sarnath@ctd.hcltech.com \
--cc=qqi@theworld.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