From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9527 invoked by alias); 1 May 2008 16:58:35 -0000 Received: (qmail 9519 invoked by uid 22791); 1 May 2008 16:58:34 -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:57:56 +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 m41GvYaI014712; Thu, 1 May 2008 09:57:34 -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:57:33 -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:57:33 -0700 Message-ID: <4819F64A.3020006@windriver.com> Date: Thu, 01 May 2008 16:58:00 -0000 From: Pawel Piech User-Agent: Thunderbird 1.5.0.14ubu (X11/20080306) MIME-Version: 1.0 To: Vladimir Prus CC: gdb@sources.redhat.com 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> <4819F019.3030402@windriver.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; 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/msg00006.txt.bz2 Vladimir Prus wrote: > Pawel Piech wrote: > > >> 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. >> > > This is not actually. The plan is for eery command will accept --thread. > Those that don't have any use of it will ignore it. The only command, > at the moment, for which the meaning of --thread is not yet clear, and for > which the frontend might have to have custom decision logic, is --exec-continue. > > - Volodya > That's helpful. Unfortunately UI clients that want to have a wide user base still need to worry about old GDB versions which do not support -thread, and that was my first point in this thread. As I've seen on this mailing list there are users out there still on GDB 5.x. I expect it will take several years before support for GDB 6.8 and prior is not so important. -Pawel