This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] MI: Event notification
- From: Vladimir Prus <ghost at cs dot msu dot su>
- To: Nick Roberts <nickrob at snap dot net dot nz>, gdb-patches at sources dot redhat dot com
- Date: Thu, 04 Jan 2007 23:25:43 +0300
- Subject: Re: [RFC] MI: Event notification
- References: <17817.40495.289353.14514@kahikatea.snap.net.nz>
Nick Roberts wrote:
>
> This is another change based on Apple's work. It is part of my focus on
> improving responsivity of the frontend, along with the timing patch.
>
> The general idea is to report changes in program state to the frontend so
> that
> it only updates the parts that need it. For example, after "up"
> frame_changed_hook triggers and the frontend knows it has to update the
> locals
> display.
You mean, after "up" emitted explicitly by the user? If the frontend changes
the frame itself, it does not need any notifications.
> This means that stepping through a single frame should be much
> quicker. If GDB enters a new frame during execution, stack_changed_hook
> triggers and the frontend knows it has to update the call stack display.
> I would eventually like to add more hooks like target-changed-hook when
> the user attaches to/detaches from a process, kills the process, or
> selects a new target with the "file" command.
Is this all for user-typed commands? I wonder if notifications for those
are really needed. Reloading entire UI state after a user command does
not seem too bad -- because user is not likely to enter 10 commands per second
anyway -- and is much simpler.
> The hooks are inserted/removed through "interpreter-exec console
> cli-command"
Sorry, can you clarify?
> so I envisage not using MI commands like -exec-run,
> -exec-next, -stack-select-frame that change that state.
Again, what do you mean?
- Volodya