From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31766 invoked by alias); 26 Mar 2005 13:44:29 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 31680 invoked from network); 26 Mar 2005 13:44:22 -0000 Received: from unknown (HELO lakermmtao07.cox.net) (68.230.240.32) by sourceware.org with SMTP; 26 Mar 2005 13:44:22 -0000 Received: from white ([68.9.64.121]) by lakermmtao07.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050326134422.EDRS19214.lakermmtao07.cox.net@white>; Sat, 26 Mar 2005 08:44:22 -0500 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1DFBaT-0003zn-00; Sat, 26 Mar 2005 08:44:25 -0500 Date: Sat, 26 Mar 2005 13:44:00 -0000 From: Bob Rossi To: Eli Zaretskii Cc: GDB Subject: Re: [mi] watchpoint-scope exec async command Message-ID: <20050326134425.GA15345@white> Mail-Followup-To: Eli Zaretskii , GDB References: <20050325161239.GA12231@white> <01c53207$Blat.v2.4$3def9b00@zahav.net.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01c53207$Blat.v2.4$3def9b00@zahav.net.il> User-Agent: Mutt/1.3.28i X-SW-Source: 2005-03/txt/msg00242.txt.bz2 On Sat, Mar 26, 2005 at 03:24:10PM +0200, Eli Zaretskii wrote: > > Date: Fri, 25 Mar 2005 11:12:39 -0500 > > From: Bob Rossi > > > > (gdb) > > -break-watch param > > ^done,wpt={number="2",exp="param"} > > (gdb) > > -exec-continue > > ^running > > (gdb) > > ~"Hardware watchpoint 2 deleted because the program has left the block \n" > > ~"in which its expression is valid.\n" > > *stopped,reason="exited",exit-code="02" > > (gdb) > > > > Is it just a bug that there is no 'watchpoint-scope' returned? > > I think it's a bug, yes: there's one instance in breakpoint.c > (specifically, in the function insert_bp_location) that uses > printf_filtered instead of the ui_* functions to produce the warning > about a watchpoint that went out of scope. I think it should use the > same code that is used by watchpoint_check to produce a similar > warning. OK, I'll look into fixing this. Bob Rossi