Re: MI output command error

[Bob Rossi <bob@brasko.net>]

On Thu, Mar 10, 2005 at 11:13:09AM -0500, Daniel Jacobowitz wrote:
> On Thu, Mar 10, 2005 at 11:08:52AM -0500, 'Bob Rossi' wrote:
> > > > That's why I think the output
> > > > 
> > > >    (gdb)
> > > >    444-exec-continue
> > > >    444*running
> > > >    444*stopped...
> > > >    (gdb)
> > > > 
> > > > is better.
> > > 
> > >   Well, you're wrong.  "running" is the output from the exec-continue
> > > command and it is synchronous: the exec-continue command executes, starts up
> > > the inferior, prints out "running", and is then complete.  At that point the
> > > inferior is running, but regardless of that, gdb is ready to take more
> > > commands and so should prompt you.  
> > 
> > It is? It is still busy executing the inferior. I was under the
> > impression GDB was somehow "busy" while executing the inferior. Is this
> > not true?
> 
> Not necessarily; some targets are asynhronous.

Hi Daniel,

The whole idea of GDB being asyncronous is new to me. Up until now, I
have been very content thinking that GDB would become "busy" whenver the
inferior was started up to do some work.

I would really like to understand the concept and the reason why GDB had
to have the asyncronous feature. While looking for documentation on GDB 
being asyncronous, I've only found very little. A grep of gdb.texino 
yeilded me nothing interesting.

I noticed that the command line option is not documented in the manual.
Which made me think it didn't exist. However, when I run gdb --help,
it's there.  
   gdb --help
   --[no]async        Enable (disable) asynchronous version of CLI

When I try to use the option, it fails,

$ gdb --async ./main
gdb: unrecognized option `--async'
Use `gdb --help' for a complete list of options.

$ gdb --noasync ./main
gdb: unrecognized option `--noasync'
Use `gdb --help' for a complete list of options.

Am I doing something wrong?

Thanks,
Bob Rossi