This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: =frame-selected MI notification
- From: Vladimir Prus <vladimir at codesourcery dot com>
- To: tromey at redhat dot com
- Cc: gdb-patches at sources dot redhat dot com
- Date: Tue, 1 Sep 2009 09:35:25 +0400
- Subject: Re: =frame-selected MI notification
- References: <87iqg99xb5.fsf@sphinx.net.ru> <h77sng$i8o$1@ger.gmane.org> <m3ljkzy3x8.fsf@fleche.redhat.com>
On Tuesday 01 September 2009 Tom Tromey wrote:
> >>>>> "Volodya" == Vladimir Prus <vladimir@codesourcery.com> writes:
>
> Volodya> Furthermore, I do not think that observers for either thread or
> Volodya> frame changes is good idea, design wise. The fact that gdb has
> Volodya> current thread or current frame at the code level, is, IMNSHO,
> Volodya> a design bug.
>
> I agree, for the core. But, the problem in question concerns
> notification about the changes to the user's view.
>
> E.g., it wouldn't be unreasonable to want to write a Python script that
> reacts to changes in the CLI's notion of frame. In this case, such an
> observer would be useful and appropriate.
Why would you want this? To implement some 'plugin' to CLI interface?
Then, since current_ptid is essentially "CLI current thread", such a
plugin naturally need observer to notice changes of current_ptid.
However, this does not say MI should use the same observer ;-)
- Volodya