From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10674 invoked by alias); 17 Jun 2009 01:04:18 -0000 Received: (qmail 10666 invoked by uid 22791); 17 Jun 2009 01:04:17 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 17 Jun 2009 01:04:11 +0000 Received: (qmail 27982 invoked from network); 17 Jun 2009 01:04:09 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 17 Jun 2009 01:04:09 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [patch] gdbserver: qXfer multiprocess Date: Wed, 17 Jun 2009 01:04:00 -0000 User-Agent: KMail/1.9.10 Cc: Aleksandar Ristovski References: <200906162209.37405.pedro@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906170204.45325.pedro@codesourcery.com> X-IsSubscribed: yes 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: 2009-06/txt/msg00424.txt.bz2 On Wednesday 17 June 2009 01:56:06, Aleksandar Ristovski wrote: > Pedro Alves wrote: > > On Tuesday 16 June 2009 21:10:14, Aleksandar Ristovski wrote: > > > >> This adds check for multiprocess before appending > >> 'multiprocess' to reply. > > > > I can see that from the patch. But, why? > > > > If gdbserver doesn't have support for multiple processes, > how will it report lack of that feature to GDB? By querying the target, how else? Something like: + if (target_supports_multi_process ()) strcat (own_buf, ";multiprocess+"); if (target_supports_non_stop ()) strcat (own_buf, ";QNonStop+"); (that function doesn't exist today, but it should). > I have created gdbserver for nto to be able to use gdb for > nto/linux. One of things this server will not have (at least > for now) is multi process support. It will only handle one > process a time. That is different from (like your patch was doing) reporting multi_process support if GDB reports support as well, which is still broken in your example. (and now that you mention it, in all gdbserver targets but linux). -- Pedro Alves