From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28785 invoked by alias); 12 Mar 2014 19:27:11 -0000 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 Received: (qmail 28767 invoked by uid 89); 12 Mar 2014 19:27:10 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 12 Mar 2014 19:27:09 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s2CJR897020734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 12 Mar 2014 15:27:08 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s2CJR63n016017; Wed, 12 Mar 2014 15:27:07 -0400 Message-ID: <5320B50A.3050308@redhat.com> Date: Wed, 12 Mar 2014 19:27:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Tom Tromey CC: gdb-patches@sourceware.org Subject: Re: [RFC v5] fix regressions with target-async References: <1394642546-10555-1-git-send-email-tromey@redhat.com> <532096DD.2020201@redhat.com> <87wqfzkzm4.fsf@fleche.redhat.com> In-Reply-To: <87wqfzkzm4.fsf@fleche.redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-03/txt/msg00296.txt.bz2 On 03/12/2014 07:04 PM, Tom Tromey wrote: > > That approach is fine with me too. Then you can remove the odd linkage > between the "maint" and target-async settings. I would like remove that also for another reason: The idea of "maint set target-async off" is to disable _target_ async support, to emulate, say sync Windows testing, on Linux. Currently, on a non-async-capable target, "set target-async on" itself does not error, but subsequent (CLI or MI) execution commands fail with "Asynchronous execution not supported on this target.". After the async-by-default series, "set target-async" becomes exclusively an MI command. After "set target-async on", MI execution commands are background execution commands. Therefore, the combination: "maint set target-async off" + "set target-async on" should also result in the same exact error as today you get when you try "set target-async on" against a target that doesn't support async. The linkage in v5 means that "set target-async on" in the testsuite re-enables "maint set target-async on", which defeats the purpose of the maint setting. (btw, I'm considering adding "set mi-async", and making "set target-async" a deprecated alias to that, for clarity) -- Pedro Alves