Re: MI output command error

[Bob Rossi <bob at brasko dot net>]

On Thu, Mar 10, 2005 at 04:36:59PM +0300, Karganov Konstantin wrote:
> 
> > Yeah, but even using the TOKENS doesn't work. The problem is, whenver I
> > front end get's a "(gdb)\r\n" it knows that it can send another command.
> > When you use the tokens with this command, you end up with,
> > 
> >    (gdb) 
> >    444-exec-continue
> >    444^running
> >    (gdb) 
> >    444*stopped,reason="watchpoint-scope",wpnum="2",thread-id="0",frame={addr="0x40039dc9",func="__libc_start_main",args=[],from="/lib/libc.so.6"}
> >    (gdb) 
> > 
> > This is still incorrect. The front end would have to know that the first
> > MI output command was not the end of the output from the single MI
> > input command. In other words, the FE would have to hardcode the fact
> > that the -exec-continue command may output 2 MI output commands. This
> > can't be correct, it would be better if the output is changed to,
> 
> If I were the GDB maintainer, I'd answer the following:
> All "execution" commands (continue, step, next, etc) are partially 
> asynchronous - in the sence that when the execution is started you can 
> type a characters to inferior stdin. In this case you need a way to know 
> when the inferior starts/stops execution.

Are you suggesting that you are using the MI with putting the inferior
on a separate pty?

Thanks,
Bob Rossi