From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9084 invoked by alias); 9 Dec 2013 12:01:41 -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 9070 invoked by uid 89); 9 Dec 2013 12:01:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from Unknown (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 09 Dec 2013 12:01:40 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id rB9C1W1C007584 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 9 Dec 2013 07:01:33 -0500 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id rB9C1V4j016929; Mon, 9 Dec 2013 07:01:31 -0500 Message-ID: <52A5B11A.4060900@redhat.com> Date: Mon, 09 Dec 2013 12:01: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: [PATCH v4 9/9] enable target-async References: <1382464769-2465-1-git-send-email-tromey@redhat.com> <1382464769-2465-10-git-send-email-tromey@redhat.com> <52828856.9070904@redhat.com> <87li0qve9y.fsf@fleche.redhat.com> <528A2E8B.9050300@redhat.com> <87r49piu9z.fsf@fleche.redhat.com> In-Reply-To: <87r49piu9z.fsf@fleche.redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-12/txt/msg00334.txt.bz2 On 12/06/2013 08:44 PM, Tom Tromey wrote: >>>>> -# so the stop reason is printed into MI uiout an. >>>>> -if {$async} { >>>>> - set reason "end-stepping-range" >>>>> -} else { >>>>> - set reason "" >>>>> -} >>>>> +set reason "end-stepping-range" >>> > Pedro> I'm a little confused by this one. Isn't it still necessary > Pedro> for targets that don't do async? > > I re-examined this and I think the answer is much simpler than all the > incorrect things I wrote before. > > git master gdb in the default (target-async off) mode prints: > > *stopped,frame={addr="0x0000000000400597",func="callee4",args=[],file="../../../binutils-gdb/gdb/testsuite/gdb.mi/basics.c",fullname="/home/tromey/Space/SecondArcher/binutils-gdb/gdb/testsuite/gdb.mi/basics.c",line="26"},thread-id="1",stopped-threads="all",core="0" > > The gdb from this branch prints: > > *stopped,reason="end-stepping-range",frame={addr="0x0000000000400597",func="callee4",args=[],file="../../../binutils-gdb/gdb/testsuite/gdb.mi/basics.c",fullname="/home/tromey/gnu/gdb/devel/binutils-gdb/gdb/testsuite/gdb.mi/basics.c",line="26"},thread-id="1",stopped-threads="all",core="3" > > But that was on GNU/Linux, where the backend will always be async, right? > That is, gdb now emits reason="end-stepping-range". This is a > compatible change to the output. This explains the patch: now the > !$async case is no longer hit. The question is whether that is actually true on all the other backends/targets that _don't_ know how to async. Like e.g., Windows. -- Pedro Alves