From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Received: (qmail 5788 invoked from network); 10 Jan 2003 22:25:25 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by 209.249.29.67 with SMTP; 10 Jan 2003 22:25:25 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h0ALvJB01387 for ; Fri, 10 Jan 2003 16:57:19 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h0AMPDa02627 for ; Fri, 10 Jan 2003 17:25:13 -0500 Received: from localhost.redhat.com (romulus-int.sfbay.redhat.com [172.16.27.46]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h0AMPBS03991; Fri, 10 Jan 2003 17:25:12 -0500 Received: by localhost.redhat.com (Postfix, from userid 469) id 19D0EFF79; Fri, 10 Jan 2003 17:29:34 -0500 (EST) From: Elena Zannoni MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15903.18765.971760.699556@localhost.redhat.com> Date: Fri, 10 Jan 2003 22:25:00 -0000 To: Daniel Jacobowitz Cc: Elena Zannoni , gdb-patches@sources.redhat.com Subject: Re: [RFA/PATCH] breakpoint.c: fix until command In-Reply-To: <20030109015304.GB8431@nevyn.them.org> References: <3E1621FF.A822AD5C@redhat.com> <15894.9086.849437.238762@localhost.redhat.com> <3E162537.63F529DF@redhat.com> <20030104015356.GA23728@nevyn.them.org> <15897.65265.595543.449396@localhost.redhat.com> <3E1A2CE3.9325A6F@redhat.com> <15898.12832.906305.726378@localhost.redhat.com> <3E1A36AD.78DAFA63@redhat.com> <20030107043155.GA5806@nevyn.them.org> <15900.41570.285605.939997@localhost.redhat.com> <20030109015304.GB8431@nevyn.them.org> X-SW-Source: 2003-01/txt/msg00427.txt.bz2 Daniel Jacobowitz writes: > On Wed, Jan 08, 2003 at 05:12:50PM -0500, Elena Zannoni wrote: > > Daniel Jacobowitz writes: > > > > > > > > I'd be happier if those two behaviors had different names, but the > > > > > > > > logical name I'd give to both of them is "until", so I guess we'll just > > > > > > > > have to live with this. (3) is meaningful when inside the function > > > > > > > > too, and with this scheme there's no way to express that without using > > > > > > > > breakpoints; but I think that's a small loss. > > > > > > > > > > > > > > > > > > > > > > Actually I start to believe that we need 2 separate commands. One > > > > > > > would do the current behavior the other would be w/o frame check. We > > > > > > > already have 'jump' (and it means something different). Maybe 'goto'? > > > > > > > I can't think of a decent name. 'reach', 'get to'? > > > > > > > > > > > > run-to? > > > > > > I like the idea of restricting "until" to the current function, > > > > > > and using a separate command for locations outside the current function. > > > > > > (or inside, if you want the effect of a temporary breakpoint). > > > > > > This would remove the ambiguity. > > > > > > > > > > I think that if we can find a decent name, there is more agreement > > > > > towards separating the behaviors. Except that 'run' in gdb means start > > > > > from the beginning, so runto can be ambiguous (it is also used in the > > > > > testsuite a lot with the meaning of start over). > > > > > > > > Ah, that's right. I was thinking of that usage, but I forgot > > > > that it starts from the beginning. > > > > > > > > Doesn't the testsuite also have a similar command that means > > > > "set a breakpoint here and continue till you get there"? > > > > > > Yes, it's gdb_continue_to_breakpoint, but it's not quite the same. > > > > > > I asked my official layperson for ideas on what to call this, and got > > > back: > > > "until first foo.c:40" > > > "until current foo.c:40" > > > > > > With a little massaging, how about one of: > > > "until first " > > > "until-first " > > > "until -first " > > > ? > > > > > > Me, I'm partial to the third form; then you can have: > > > until -first func > > > until -current func > > > > > > > I am not clear what first vs. current means. You mean first as 'first > > time you cross' that given location? So you would drop the "called > > from the current frame" restriction. > > Yeah, that was my basic idea. > > > > And make one of those the default. But this is risks starting the > > > argument about syntax of options to CLI commands all over again. It > > > seems to me that these are both logical things to do for "until", so > > > why not call them both "until", if we can agree on a syntax? > > > > > > > I don't much like having options, it's too much to type. :-) I think > > we should leave the until as it is, name and all. Or it will confuse > > people even more. I like 'to' as a possible simple name for the other > > form. Or 'through'. > > The problem is, neither to or through makes sense to me as an option; I > can't figure out what it will do. > Not as an option, I was thinking as a separate command. (to tell you the through, it should just be an argument to 'continue'). Elena > -- > Daniel Jacobowitz > MontaVista Software Debian GNU/Linux Developer