This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: The main event(s)...
Keith Seitz wrote:
>
> Hi,
>
> Well, I think we're at the point where we need to really start cleaning up
> Insight.
>
> Fernando has already started a plugin class (thanks Fernando!), and it
> occurred to me while looking over the code: It isn't at all obvious
> what events are communicated from gdb to Insight.
>
> In an effort to identify these events, I would like to propose the following
> cleanup:
>
> Currently, windows/widgets register for events from gdb by using "add_hook".
> For example, to register with the GUI what to do when the target's state
> has changed (stopped executing or a stack frame change by the user), windows
> would do something like this:
Two comments:
o one day, gdb really will become
async. at that point the basic
assumption that target_running
== !target_not_running will
go out the window.
While I'd ignore this for now
just keep it in mind.
o the way GDB feeds events up
to insight is pretty bogus
If you can, try to figure out
some generic operations
so that gdb can feed them up
(rather than the current
really really specific events)
Rather than wait for GDB to
do this for you, could I suggest
creating a layer that sits
between GDB and INSIGHT and
have that massage the current
events into something more
meaningful.
That should avoid the problem
of INSIGHT constantly wanting
to change the event hooks
in GDB.
Andrew