This is the mail archive of the
mailing list for the GDB project.
Re: Questions about GDB-MI Interface
> 2. On the same topic, when we use CLI-in-MI we see that we sometimes get
> pure CLI output, sometimes pure MI output, and sometimes a mixture of
> both. The Users Guide hints that this is normal, when it says to expect
> an "unsupported hybrid of GDB/MI and CLI output", but we don't know if we
> can provide a reliable and high-fidelity console window under these
> conditions. Do you have any suggestions how we should proceed, or how
> other front ends have dealt with this?
> Ideally, we'd like to let our users continue to use the CLI, and see
> CLI-style output, while our GUI simultaneously interacts with gdb using MI.
> So we'd like to change the definition of MI to support this, and have all
> commands change their output style based on whether they are invoked via
> the CLI or MI.
> We found one of the recent discussions from GDB Mailing List addressing
> this specific problem:
> Apple has implemented a solution to allow front-ends to switch GDB's
> interpreter between MI and CLI. This solution will allow frontend to relay
> commands entered by user to GDB, and responses coming back from GDB will be
> in CLI-style. CLI-style responses can be sent back to our console window
> and will be meaningful to users.
Can I encourage you to look at Apple's contributed code. See:
As was noted by JimI, they came up with a way to address the problem.
You could even consider extracting the relevant changes from the patch.
However, before doing this, you would need to establish a GDB
With regard to annotations and using GDB's CLI directly, I really would
discourage this. They are both largely untested(1) and make your code
reliant on the behavour of the underlying CLI (something you can assume
(1) Some what ironically, it was the MI developers that added the
annotation tests to GDB.