From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: multi-process remote protocol extensions
Date: Tue, 03 Jun 2008 17:12:00 -0000 [thread overview]
Message-ID: <200806031812.18582.pedro@codesourcery.com> (raw)
In-Reply-To: <200806031804.11363.pedro@codesourcery.com>
A Tuesday 03 June 2008 18:04:11, Pedro Alves wrote:
> A Tuesday 03 June 2008 17:13:40, Daniel Jacobowitz wrote:
> > 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.
>
> Hmmm, no, this is a separate issue to multiprocess, it affects
> single-process stubs as well, e.g., native Windows gdbserver is
> replying 'W' AA, but the exit code of a Windows process isn't
> limited to 8-bits. It should be reported as a separate
> feature, I guess.
(lamely replying to myself)
Well, if GDB starts announcing multi process in the same
release it supports more than two nibbles, all should be fine,
the stub can rely on the multi-process support check. I'm in
no hurry to fix this, so, I'm ok with the wait. :-)
Not as clean, but avoids growing the qSupported string.
--
Pedro Alves
next prev parent reply other threads:[~2008-06-03 17:12 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
2008-06-03 17:04 ` Pedro Alves
2008-06-03 17:12 ` Pedro Alves [this message]
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=200806031812.18582.pedro@codesourcery.com \
--to=pedro@codesourcery.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