From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12861 invoked by alias); 11 Jul 2014 17:27:01 -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 12814 invoked by uid 89); 11 Jul 2014 17:26:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS 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 (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 11 Jul 2014 17:26:57 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s6BHQsR6032058 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 11 Jul 2014 13:26:55 -0400 Received: from barimba (ovpn-113-95.phx2.redhat.com [10.3.113.95]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s6BHQrHO019996 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Fri, 11 Jul 2014 13:26:54 -0400 From: Tom Tromey To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] fix record "run" regression References: <1404251135-2427-1-git-send-email-tromey@redhat.com> <53B3D640.2060807@redhat.com> <87ha2ynwez.fsf@fleche.redhat.com> <53B6BCFF.90703@redhat.com> <87r41xi3v2.fsf@fleche.redhat.com> <53BBB93B.9060207@redhat.com> Date: Fri, 11 Jul 2014 18:05:00 -0000 In-Reply-To: <53BBB93B.9060207@redhat.com> (Pedro Alves's message of "Tue, 08 Jul 2014 10:26:19 +0100") Message-ID: <871ttr7qn7.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2014-07/txt/msg00285.txt.bz2 >>>>> "Pedro" == Pedro Alves writes: Pedro> The comment is stale now. If we can indeed use gdb_run_cmd, Pedro> then I don't think we need the $use_gdb_stub check? The use_gdb_stub check is there so that we skip the test on target remote, which I think shouldn't be expected to work, as you can't re-run there. But I think I must be missing something. Tom