From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-31746-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 8110 invoked by alias); 27 Apr 2008 07:51:39 -0000
Received: (qmail 8102 invoked by uid 22791); 27 Apr 2008 07:51:38 -0000
X-Spam-Check-By: sourceware.org
Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.25)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 27 Apr 2008 07:51:13 +0000
Received: from kahikatea.snap.net.nz (208.62.255.123.dynamic.snap.net.nz [123.255.62.208]) 	by viper.snap.net.nz (Postfix) with ESMTP id B73983DB231; 	Sun, 27 Apr 2008 19:51:05 +1200 (NZST)
Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) 	id 741218FC6D; Sun, 27 Apr 2008 19:50:58 +1200 (NZST)
From: Nick Roberts <nickrob@snap.net.nz>
Message-ID: <18452.12385.71094.702844@kahikatea.snap.net.nz>
Date: Mon, 28 Apr 2008 00:15:00 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sources.redhat.com
Subject: Re: [MI] enabling non-stop mode
In-Reply-To: <fv1655$ck3$1@ger.gmane.org>
References: <200804262216.16948.vladimir@codesourcery.com> 	<18451.45027.743862.885534@kahikatea.snap.net.nz> 	<fv1655$ck3$1@ger.gmane.org>
X-Mailer: VM 7.19 under Emacs 22.2.50.2
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-04/txt/msg00228.txt.bz2

 > >  > Probably, we can extend this to enable feature that are not MI proper,
 > >  > say:
 > >  > 
 > >  > (gdb) -list-features
 > >  >         ^done,features=[....,"non-stop",....]
 > >  > (gdb) -enable-feature non-stop
 > >  > ^done
 > >  > 
 > >  > The only issue here is that non-stop mode availability in general
 > >  > depends on the target, so maybe we should have a separate commands
 > >  > to list "target" feature and then enable target features?
 > > 
 > > Why not just use -gdb-set?
 > > 
 > > maint set linux-async   -->  set linux-async  -->  -gdb-set linux-async
 > > maint set non-stop      -->  set  non-stop    -->  -gdb-set non-stop
 > 
 > This will now allow the frontend to check if non-stop mode is supported at
 > all.

I mean list "non-stop" as a feature, which AFAICS just outputting a string
field, _and_ do:

    add_setshow_boolean_cmd ("non-stop",...

I don't see the benefit of another MI command like -enable-feature and
that way non-stop mode can be more easily made available to CLI.

-- 
Nick                                           http://www.inet.net.nz/~nickrob