This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [vxworks 02/14] New command_post observer.


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

Joel> The problem is that we cannot just print a message everytime the PD
Joel> gets switched, because many commands result in a temporary switch of
Joel> partition.

Joel> The way we solved this is by remembering the PD ID before we issued
Joel> the last command.  At the end of a command execution, if the PD ID
Joel> changed, then we write a notification...

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

There are a lot of calls to execute_command that occur in batch-like
places.  For example, this is called from Python, I think it is called
from "commands" scripts and "define" scripts, etc.

So if your goal is to have it just emit info at some stopping point, it
seems to me that it would be better to have an observer just before a
prompt is emitted.

I didn't read every patch in detail, so I didn't see where this is used.
Maybe the above doesn't matter.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]