From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: multi-process remote protocol extensions
Date: Tue, 03 Jun 2008 16:14:00 -0000 [thread overview]
Message-ID: <20080603161340.GA20861@caradoc.them.org> (raw)
In-Reply-To: <200806031654.47008.pedro@codesourcery.com>
On Tue, Jun 03, 2008 at 04:54:46PM +0100, Pedro Alves wrote:
> > > Not stricly multi-process related, but while we're at it, two
> > > nibbles `AA' only is unnecessarilly limiting. That was
> > > the other reason for proposing new status packets.
> >
> > Allow more than just two nibbles if gdb supports the semicolon?
>
> How can the stub know if GDB supports the semicolon?
By the multiprocess announcement, I suppose. We already needed to
know this since ;process would break otherwise.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-06-03 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 17:18 Pedro Alves
2008-05-30 13:15 ` Michael Snyder
2008-05-30 13:35 ` Pedro Alves
2008-06-03 1:28 ` Daniel Jacobowitz
2008-06-03 15:20 ` Pedro Alves
2008-06-03 15:42 ` Daniel Jacobowitz
2008-06-03 15:55 ` Pedro Alves
2008-06-03 16:14 ` Daniel Jacobowitz [this message]
2008-06-03 17:04 ` Pedro Alves
2008-06-03 17:12 ` Pedro Alves
2008-06-03 17:31 ` 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=20080603161340.GA20861@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.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