Re: [patch:MI] Observer for thread-changed

[Nick Roberts <nickrob at snap dot net dot nz>]

 > > I think that the Python layer would like to be notified of every
 > > thread change.  That way, it will be possible to write Python
 > > libraries which react to these kinds of events.
 > 
 > I can tell you this. The annotate-1 interface used to send out things
 > like breakpoints-changed whenever something happened that triggered a
 > breakpoint change. This data would come out so fast, it would effect the
 > performance of the front end from getting meaningful data.

You mean level 2 annotations?  Level 1 annotations is just --fullname which
only emits the one (source) annotation.  Yes, it does fire too frequently.  I
don't know why, but I think it fires when the breakpoints are removed and
re-inserted each time execution stops.

 > I'm just giving a little advice, make sure that gdb doesn't auto send
 > out information if the inferior can manipulate itself in such a way that
 > it would effectively flood the communication between gdb and the front
 > end.
 > 
 > Can thread changes happen often? how often? how will this effect the
 > communication load?

I think it can only change, at most, once every time execution stops and
when the user selects a new thread.  So the load is very light.

-- 
Nick                                           http://www.inet.net.nz/~nickrob