Re: asynchronous MI output commands

[Nick Roberts <nickrob@snap.net.nz>]

 > I just happened to notice that -exec-next and -interpreter-exec console
 > next are surprisingly different.
 > 
 > (gdb)
 > -exec-next
 > ^running (gdb)
 > *stopped,reason="end-stepping-range",thread-id="0",frame={addr="0x0804836b",func="main",args=[{name="argc",value="1"},{name="argv",value="0xbf80e254"}],file="main.c",line="5"}
 > (gdb)
 > -interpreter-exec console next
 > ~"6\t  return 0;\n"
 > ^done
 > (gdb)

The branch that I want to create, when I have proper internet access, will
give asynchronous output (*stopped) for both commands.

 > Is next asynchronuos in 1 case and not the other?

They're both synchronous at the moment (the "*stopped" for -exec-next is faked).

Bob, I would guess that MI output is likely to continue to change so I would
try to factor that into your parser.

-- 
Nick                                           http://www.inet.net.nz/~nickrob