Re: Re-initializing a list after the control returns to gdb...

[Joel Brobecker <brobecker@gnat.com>]

> The code relies on global state so I think `target changed' is better - 
> that way you know that your state is up-to-date.  From memory, right now 
> we've actually memory_changed and registers_changed (I think they should 
> be merged).  There is also a target run hook that insight uses.

Unfortunately `target changed' does not trigger at least every time
I need it to. I looked at the code, and it should basically trigger
everytime we change some data in memory. 

A quick attempt with "set debug event 1" shows that the only events
I see in a simple "break; run" sequence are breakpoint events...

> That's the problem (you said sick), we've three:
> - gdb-events
> - chained hooks
> - simple hooks
> gdb-events started on the problem but lost direction.

I like the events mechanism, it's a paradigm that's used very widely.
But the gdb-event mechanism does not seem to allow several clients
subscribing for these events at the same time. This mechanism is
then very close to the simple hooks.

I am therefore thinking of implementing a new chained hook in place
of the direct call to ada_read_tasks_list. Would that be an acceptable
solution?

-- 
Joel