Re: [PATCH 02/18] New command_post observer

Tom Tromey
2011-02-24T18:58:22Z

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> What we are trying to do is to keep the user informed of the current
Joel> PD (which is identified by either PD ID or name, but we like to print
Joel> both).

I have a patch kicking around here to add prompt substitutions to gdb.
This might be a nice fit for this use.

I can try to submit this soon if you think it is worthwhile. I wasn't
really sure.

Joel> This patch introduces an observer (command_post) that gets triggered
Joel> at the end of a command execution...

I think an observer for this is fine...

Joel> (execute_command): Call observer_notify_command_post.

... but putting it here seems a little strange.
I think this will trigger after any command that is executed, including
commands in "command" or in a "define" or via Python's gdb.execute.

I would have thought that a "top-level" notification would have been
more along the lines of what you wanted.

Tom