From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12869 invoked by alias); 18 Oct 2013 15:26:02 -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 12857 invoked by uid 89); 18 Oct 2013 15:26:02 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 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 ESMTP; Fri, 18 Oct 2013 15:26:01 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r9IFPxSp017849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 18 Oct 2013 11:25:59 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r9IFPwCH011575; Fri, 18 Oct 2013 11:25:58 -0400 Message-ID: <52615305.3050909@redhat.com> Date: Fri, 18 Oct 2013 15:26: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: Andrew Burgess CC: "gdb-patches@sourceware.org" Subject: Re: [PATCH] hardware watchpoints turned off, inferior not yet started References: <525E5EB6.4070305@broadcom.com> <525E8761.8060405@redhat.com> <525EB424.6010407@broadcom.com> <525EBEA7.5060205@redhat.com> <5260FBE3.8030200@broadcom.com> In-Reply-To: <5260FBE3.8030200@broadcom.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-10/txt/msg00569.txt.bz2 On 10/18/2013 10:14 AM, Andrew Burgess wrote: > After my patch then we do indeed see the error earlier, when the second > "file foo" is issued. BTW, not super important, but thinking out loud, I think it'd make sense to have the "set can-use-hw-watchpoints" command itself trigger a breakpoint/watchpoint reset. -- Pedro Alves