From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4468 invoked by alias); 22 Jun 2003 19:19:12 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 4372 invoked from network); 22 Jun 2003 19:19:10 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 22 Jun 2003 19:19:10 -0000 Received: from dsl093-172-017.pit1.dsl.speakeasy.net ([66.93.172.17] helo=nevyn.them.org ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 19UANc-0002ng-00; Sun, 22 Jun 2003 14:20:00 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19UAMj-0001nS-00; Sun, 22 Jun 2003 15:19:05 -0400 Date: Sun, 22 Jun 2003 19:19:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney , gdb-patches@sources.redhat.com Subject: Re: RFC: Syntax for logging Message-ID: <20030622191904.GB606@nevyn.them.org> Mail-Followup-To: Andrew Cagney , gdb-patches@sources.redhat.com References: <20030621172358.GA8711@nevyn.them.org> <3EF5EFAD.6010401@redhat.com> <20030622180719.GA7389@nevyn.them.org> <3EF5F649.6050809@redhat.com> <20030622184141.GA606@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030622184141.GA606@nevyn.them.org> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-06/txt/msg00710.txt.bz2 On Sun, Jun 22, 2003 at 02:41:41PM -0400, Daniel Jacobowitz wrote: > On Sun, Jun 22, 2003 at 02:32:41PM -0400, Andrew Cagney wrote: > > > > > >Hmm, two options: > > > set logging > > > > Not this. It should behave like: > > > > (gdb) set architecture > > "set architecture" must be followed by "auto" or an architecture name. > > OK. > > > > > > unset logging > > > > > >I like "unset logging"; how about you? The only thing we use unset for > > >at the moment is "unset environment" but I think it extends naturally. > > > > so (slightly wierd) yes this. Be sure to mention it in the help > > message. Perhaphs, also accept ``set logging off'', and ``set logging > > on'' as those are the first things I'd try :-) > > > > Hmm, just noticed, the options are optional, I was thinking that they > > were required. > > > > set logging [redirect|log] [append|overwrite] FILE > > > > The syntax will lead to confusion with things like: > > > > set logging l > > or > > set logging redirect a > > Ugh, I'd forgotten about the abbreviations. > > > suggest instead: > > > > set logging on [FILE] > > default gdb.log, log, append? > > set logging off > > set logging file FILE > > set logging append {true,false} > > set logging redirect {true,false} > > > > so that the [FILE] isn't context dependent. Realisticly, I think people > > will only use: > > > > set logging on > > set logging off > > That looks good. I'll just ditch the unset idea. Hmm, what do you think of this idea? The above set commands, and also: log file CMD "log" will obey "set logging append" and "set logging redirect". An alternative, even simpler: log CMD "log" will obey append, redirect, and file, but works even when logging is off. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer