This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: Re-initializing a list after the control returns to gdb...
- From: Joel Brobecker <brobecker at gnat dot com>
- To: Andrew Cagney <ac131313 at redhat dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Wed, 19 Feb 2003 09:50:56 -0800
- Subject: Re: Re-initializing a list after the control returns to gdb...
- References: <20030219020101.GI2105@gnat.com> <3E53B97A.4090809@redhat.com>
> You've the `observer' problem.
Just like when you are sick, you already feel better when you know which
disease you have contracted :).
> GDB's observer code is very primative. A combination of gdb-events
> (needs direction) and chained hooks (see target_new_objfile_hook).
>
> I suspect what you really want is a `target changed' event.
I need to update the task list every time the inferior stops and
the control returns to the user. I think the `target change' event
is not exactly what I would need?
Do we have a list of currently supported events? Is there a framework
for implementing these events?
--
Joel