From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11547 invoked by alias); 30 Aug 2011 17:29:21 -0000 Received: (qmail 11536 invoked by uid 22791); 30 Aug 2011 17:29:19 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 30 Aug 2011 17:29:06 +0000 Received: (qmail 5209 invoked from network); 30 Aug 2011 17:29:05 -0000 Received: from unknown (HELO scottsdale.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 30 Aug 2011 17:29:05 -0000 From: Pedro Alves To: Tom Tromey Subject: Re: [RFC] stept, nextt, finisht, untilt, continuet Date: Tue, 30 Aug 2011 17:29:00 -0000 User-Agent: KMail/1.13.6 (Linux/2.6.38-11-generic; KDE/4.7.0; x86_64; ; ) Cc: gdb-patches@sourceware.org, Doug Evans , Jan Kratochvil , pfee@talk21.com References: <20110830014851.78030246131@ruffy.mtv.corp.google.com> <201108301621.55098.pedro@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201108301829.03121.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-08/txt/msg00617.txt.bz2 On Tuesday 30 August 2011 18:13:05, Tom Tromey wrote: > >>>>> "Pedro" == Pedro Alves writes: > > Pedro> I'm currently working towards adding (run control) ptset/itset > Pedro> support to gdb. Working on instructure still (I can run all-stop on > Pedro> top of a target running in non-stop mode now), and the final syntax > Pedro> will obviously need discussion, but I think we could come up with > Pedro> syntax for this within that framework. > > I think it would be good to flesh out the syntax details now. > Maybe you could post your proposal; or even just a link to the earlier > proposal if you plan to follow it. Will do, either I or Stan. I've been focused on target async and infrustructure leg work, so haven't really thought much on syntax. I think the main options to discuss will be prefix syntax, or new options to execution commands syntax. Hopefuly this week or the next I'll have enough glue to go through this and experiment a bit. > It would be helpful to the ambiguous linespec work if the basic ptset > code (stuff relating to the data structure itself, not wiring it into > inferior control) were available "early" -- I'm away for a bit, and I > don't know your schedule, so it all may be fine; but I mean sometime in > October. Hopefuly sooner. -- Pedro Alves