From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22401 invoked by alias); 15 Jan 2013 19:55:26 -0000 Received: (qmail 22388 invoked by uid 22791); 15 Jan 2013 19:55:25 -0000 X-SWARE-Spam-Status: No, hits=-7.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SARE_SUB_OBFU_Q1,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 15 Jan 2013 19:55:18 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r0FJtFFg013230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 15 Jan 2013 14:55:16 -0500 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r0FJtEr7001830; Tue, 15 Jan 2013 14:55:14 -0500 Message-ID: <50F5B421.8040605@redhat.com> Date: Tue, 15 Jan 2013 19:55:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Yao Qi CC: gdb-patches@sourceware.org Subject: Re: [PATCH,gdbserver] Put 'multiprocess+' in to qSupported reply if GDB supports multiprocess References: <1358240468-11484-1-git-send-email-yao@codesourcery.com> In-Reply-To: <1358240468-11484-1-git-send-email-yao@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2013-01/txt/msg00322.txt.bz2 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