From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31792 invoked by alias); 2 Sep 2011 23:28:36 -0000 Received: (qmail 31782 invoked by uid 22791); 2 Sep 2011 23:28:35 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-yi0-f41.google.com (HELO mail-yi0-f41.google.com) (209.85.218.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 02 Sep 2011 23:28:16 +0000 Received: by yib2 with SMTP id 2so2703140yib.0 for ; Fri, 02 Sep 2011 16:28:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.145.10 with SMTP id o10mr8677677yhj.90.1315006095785; Fri, 02 Sep 2011 16:28:15 -0700 (PDT) Received: by 10.236.61.34 with HTTP; Fri, 2 Sep 2011 16:28:15 -0700 (PDT) In-Reply-To: <201109021807.41992.pedro@codesourcery.com> References: <201109021807.41992.pedro@codesourcery.com> Date: Sat, 03 Sep 2011 09:21:00 -0000 Message-ID: Subject: Re: Flip the interpreter to synchronously wait for commands finishing, in command lists and similars From: Matt Rice To: Pedro Alves Cc: gdb-patches@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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-09/txt/msg00047.txt.bz2 On Fri, Sep 2, 2011 at 10:07 AM, Pedro Alves wrote: > > With this patch, synchronous execution commands (the regular step, next, > etc., that is, those with an & suffixed) with a target running > in async mode work correctly (AFAICT) with all current use cases. =A0 =A0= We > can consider flipping on async on by default, and then incrementally > convert specific paths to state machines, for new use cases, rather than > delaying flipping on async on by default until _everything_ is converted > into a state-machine. I was hoping this might fix, (but doesn't seem to) the following case: ./gdb/gdb -ex 'set target-async on' -ex 'attach 7625' -ex 'continue' ./gdb/gdb -ex 'set target-async on' -ex 'attach 7625' -ex 'continue&' both these commands exhibit: Continuing. Program received signal SIGSTOP, Stopped (signal). ..... (gdb) thus changing the behavior of '-ex continue' should we turn target-async on by default.