From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27980 invoked by alias); 1 May 2008 16:31:55 -0000 Received: (qmail 27971 invoked by uid 22791); 1 May 2008 16:31:55 -0000 X-Spam-Check-By: sourceware.org Received: from mail.windriver.com (HELO mail.wrs.com) (147.11.1.11) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 01 May 2008 16:31:33 +0000 Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m41GV95f004192; Thu, 1 May 2008 09:31:09 -0700 (PDT) Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 1 May 2008 09:31:09 -0700 Received: from [147.11.233.152] ([147.11.233.152]) by ala-mail06.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 1 May 2008 09:31:09 -0700 Message-ID: <4819F019.3030402@windriver.com> Date: Thu, 01 May 2008 16:31:00 -0000 From: Pawel Piech User-Agent: Thunderbird 1.5.0.14ubu (X11/20080306) MIME-Version: 1.0 To: Vladimir Prus CC: Pedro Alves , gdb@sourceware.org, Marc Khouzam Subject: Re: MI non-stop interface details References: <200804261939.37635.vladimir@codesourcery.com> <200804291848.51730.pedro@codesourcery.com> <481762E8.5010707@windriver.com> <200805012015.38035.vladimir@codesourcery.com> In-Reply-To: <200805012015.38035.vladimir@codesourcery.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-05/txt/msg00004.txt.bz2 Vladimir Prus wrote: > On Tuesday 29 April 2008 22:03:20 Pawel Piech wrote: > >> Pedro Alves wrote: >> >>> I can't see how is it different -- in the frontend's perspective -- >>> of keeping track of what to pass to --thread= *provided GDB doesn't switch >>> threads automatically*. But then again, I'm no frontend writer. >>> >>> >> Using -thread-select makes it easier for the front end to be compatible >> with older versions of GDB. >> > > Hmm, I though that only reason that -thread-select is simpler is because > in DSF, specifically, there's no central place where commands are send > and where --thread can be conveniently added. I'm not saying this is good, > or bad, but this is not the case for all frontend. Am I wrong? > > - Volodya > In DSF-GDB there _is_ a central place where commands are sent, this is where the protocol state is adjusted using -thread-select. However, the --thread option is being added to many but not all commands, so the same mechanism that adds the -thread-select could not be reused to add --thread option. Instead each command which accepts --thread that would need to be adjusted to use the --thread, but only when in non-stop debugging mode. -Pawel