[mi] watchpoint-scope exec async command

[Bob Rossi <bob@brasko.net>]

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