Re: [PATCH v2 8/9] Implement gdb.execute_mi

[Tom Tromey <tromey@adacore.com>]

Simon> My patch here:

Simon> https://inbox.sourceware.org/gdb-patches/48eb5ee9-53e1-f1df-b424-d08342c7e857@simark.ca/T/#m94825956483bc1d340da33ad4712752d3326fecf

Simon> conflicts with this patch, so I am taking a closer look at
Simon> gdb.execute_mi.  I think some things are missing from the gdb.execute_mi
Simon> implementation [...]

I just wanted to let you know I haven't dropped this.
I didn't look at it much but I hope to investigate a bit next week.

Simon>   (gdb) python gdb.execute_mi('-gdb-exit')

Simon> First, I think that the new mi_execute_command function should install
Simon> the mi interpreter as the current interpreter (or the command
Simon> interpreter, I don't really understand the distinction) such as code
Simon> down mi_execute_command gets the mi_interp object when calling
Simon> current_interpreter.  There are not a lot of commands getting the
Simon> current interpreter, but -gdb-exit is one of them.  I tried fixing this
Simon> quickly, but it's not just a oneliner.

I wouldn't mind disallowing -gdb-exit from execute_mi.  That's a
pathological case anyway.

I looked for calls to current_interpreter in the MI code but I don't see
many... though who knows what the core of gdb is doing.  In fact the
-gdb-exit one is the only one that seems to be part of a command.

Tom