This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH,gdbserver] Put 'multiprocess+' in to qSupported reply if GDB supports multiprocess
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 15 Jan 2013 19:55:13 +0000
- Subject: Re: [PATCH,gdbserver] Put 'multiprocess+' in to qSupported reply if GDB supports multiprocess
- References: <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