Re: RFC: MI output during program execution

[Bob Rossi <bob at brasko dot net>]

> Remember I haven't done this with observers or events yet.  The way I  
> did it with hooks, the result of the hooks is gathered into the  
> "^done" or the other termination states for the command.  So for  
> instance, if you run gdb on itself, and do:

Hi Jim,

Thanks for all the guidence so far. Even though you have not attempted
the observer approach, how do you feel about it? Is this something that
you think could be accomplished with the current FSF GDB? Nick, Daniel
and Eli, do you like this approach? I'm sure I could find some time to 
get something going in this direction, with a little bit of thought.

Anyone else willing to work towards this solution?

I really like Daniel's idea of just alerting the user that something has
changed, instead of actually giving the user the data. For instance he
had,

   =breakpoint-changed,[bpnum="1",state="disabled"]
   =thread-changed,[thread="2"]

I might even prefer,
   =breakpoint-changed,thread-changed
which would then allow the FE to call -list-breakpoints or whatever if
they are interested.

This is very similar to how annotate=2 solved the problem for when
breakpoints changed. The only wierd issue that happened with this
approach is that the data breakpoint-changed was literally outputted
thousands and thousands of times in certain circumstances. (compiled
program with optimizations).

Thanks,
Bob Rossi