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: RFC: MI output during program execution


The front end needs to know if a CLI command executed via "- interpreter-exec console" changed the current thread or frame - so it can update the UI accordingly. Or if it started the target running. Or if it added a breakpoint.

All these things could be queried from existing commands in the MI, but that's pretty inconvenient and inefficient. It's much easier to code up the UI if gdb tells it asynchronously about these things.

Jim

On Aug 9, 2005, at 10:51 AM, Bob Rossi wrote:

But as I said in my previous note, I think a better solution is to
use hooks/observers/events or whatever to allow the MI to be informed
about things it needs to know about "behind the back" of the CLI
that's running the command.


Could you please give a quick example of something "the FE needs to know
about?" Would there be a default way to get all the things the FE
cares about? Is it as easy as making a new MI command
-mi-get-state
which would output a list of items the FE cares about?


Thanks,
Bob Rossi



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