From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-21006-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 18658 invoked by alias); 25 Mar 2005 16:12:46 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 18636 invoked from network); 25 Mar 2005 16:12:40 -0000
Received: from unknown (HELO lakermmtao10.cox.net) (68.230.240.29)
  by sourceware.org with SMTP; 25 Mar 2005 16:12:40 -0000
Received: from white ([68.9.64.121]) by lakermmtao10.cox.net
          (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP
          id <20050325161236.HXUK29924.lakermmtao10.cox.net@white>
          for <gdb@sources.redhat.com>; Fri, 25 Mar 2005 11:12:36 -0500
Received: from bob by white with local (Exim 3.35 #1 (Debian))
	id 1DErQN-0003Dc-00
	for <gdb@sources.redhat.com>; Fri, 25 Mar 2005 11:12:39 -0500
Date: Fri, 25 Mar 2005 16:12:00 -0000
From: Bob Rossi <bob@brasko.net>
To: GDB <gdb@sources.redhat.com>
Subject: [mi] watchpoint-scope exec async command
Message-ID: <20050325161239.GA12231@white>
Mail-Followup-To: GDB <gdb@sources.redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
X-SW-Source: 2005-03/txt/msg00233.txt.bz2

Hi,

I've been trying to understand and document the exec-async commands that
GDB sends to the FE. So far, I think I've understood them all, and 
reproduced them. However, the "watchpoint-scope" one is giving me a hard time.

Here's the sample program, 

int wpscope ( int param ) {
    return param+1;
}

int main(int argc, char **argv){
    return wpscope ( argc );
}

$ ../gdb -i=mi ./wpscope
(gdb)
-break-insert wpscope
^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x08048357",func="wpscope",file="wpscope.c",line="2",times="0"}
(gdb)
-exec-run
^running
(gdb)
*stopped,reason="breakpoint-hit",bkptno="1",thread-id="0",frame={addr="0x08048357",func="wpscope",args=[{name="param",value="1"}],file="wpscope.c",line="2"}
(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?
The 'break-watch' doco in the manual leads me to believe that I should
get back the "watchpoint-scope" when the hardware watchpoint was
deleted. However, I don't really have any clue if this is a bug or
desired behavior.

Any help would be appreciated, since hopefully I can better document the
reasons why such events would occur.

Thanks,
Bob Rossi