Re: MI usage inside a user-defined commands

[Bob Rossi <bob at brasko dot net>]

On Thu, Jul 07, 2005 at 09:26:42AM +1200, Nick Roberts wrote:
> 
>  > I mean the "define" feature itself works fine under MI (that is expected), 
>  > but allows only CLI commands inside (that is not expected). From the first 
>  > view it looks like broken CLI-compatibility...
> 
> The manual says:
> 
>   A "user-defined command" is a sequence of GDB commands...
> 
> GDB command implicitly means CLI command.  I guess an equivalent MI command
> could be implemented to execute a sequence of MI commands, but I'm not sure
> that it would be needed.
> 
> I don't know why you expect "define", a CLI command to accept a list of
> MI commands.  Likewise, "source filename" and breakpoint command lists will
> only work with CLI commands.
> 
> What does seem wrong is that MI no longer works properly with queries:
> 
> (gdb) 
> -interpreter-exec console "b asdf"
> &"Function \"asdf\" not defined.\n"
> ~"Breakpoint 2 (asdf) pending.\n"
> ^done
> (gdb) 

I've noticed this. I was going to fix it if I had some time.
It won't work when with overloaded function breakpoints either.

Bob Rossi