Re: starting gdb/mi from FE

[Daniel Jacobowitz <drow@false.org>]

On Tue, Jun 06, 2006 at 12:54:54PM +1200, Nick Roberts wrote:
> I can't remember the previous outcome (I got lost with all the handshakes) but
> I would prefer an MI command, -mi-version say, that the FE could use.  It
> could have a major and minor part: the major number to refer to the default MI
> level; and the minor to help identify small changes made within one level.  Of
> course, we'd have to remember to update it, when appropriate.
> 
> Pre GDB 6.5 wouldn't really work in this case either, but
> 
>   (gdb)
>   -mi-version
>   ^error,msg="Undefined MI command: mi-version"
>   (gdb)
> 
> wouldn't require restarting GDB, while:
> 
>   nickrob/21 gdb -i=mi2,mi1 myprog
>   Interpreter `mi2,mi1' unrecognized
>   nickrob/22
> 
> would.

Two items.

Nick, could you explain why the restart is a problem?  The time GDB
takes to reject an interpreter doesn't seem too bad.  I don't want to
optimize the wrong thing.

Bob, since we last discussed this the interpreter commands have matured
a bit.  There's even tab completion for the CLI interpreter-exec
command; try "interpreter-exec <tab>" and you'll get a list.

Would -interpreter-list and -interpreter-set do it for you?

I thought there already was a "set interp", but it seems I was
mistaken.

-- 
Daniel Jacobowitz
CodeSourcery