From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH,gdbserver] Put 'multiprocess+' in to qSupported reply if GDB supports multiprocess
Date: Tue, 15 Jan 2013 19:55:00 -0000 [thread overview]
Message-ID: <50F5B421.8040605@redhat.com> (raw)
In-Reply-To: <1358240468-11484-1-git-send-email-yao@codesourcery.com>
On 01/15/2013 09:01 AM, Yao Qi wrote:
> GDBserver put 'multiprocess+' in to qSupported reply regardless of
> whether GDB supports multiprocess. It doesn't cause any problems
> because if GDB doesn't support multiprocess, GDB doesn't understand
> 'multiprocess+'. However, I feel it is better not to send
> 'multiprocess+' to GDB if GDB doesn't support multiprocess.
I disagree, and it's a dangerous path to follow. It may prove useful
to know what exactly does a target support even if your gdb doesn't
support it for instance, as a debugging aid. Or GDB itself may know
of a feature, but choose to not enable it (and therefore not broadcast
support in its qSupported), but still infer something about the
target from the target's reported features. So it's more prudent to
make the qSupported reported features as stateless as possible.
--
Pedro Alves
next prev parent reply other threads:[~2013-01-15 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 9:02 Yao Qi
2013-01-15 19:55 ` Pedro Alves [this message]
2013-01-16 8:31 ` Yao Qi
2013-01-16 18:18 ` Pedro Alves
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=50F5B421.8040605@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@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