Documentation issues

Documentation issues

[Nick Roberts]

The followin commands are still mentioned in the manual but appear to have been
removed (replaced by target-async?):

    `maint set linux-async'
    `maint show linux-async'
        Control the GNU/Linux native asynchronous support (*note
        Background Execution::) of GDB.

        GNU/Linux native asynchronous support will be disabled until you
        use the `maint set linux-async' command to enable it.

   `maint set remote-async'
   `maint show remote-async'
        Control the remote asynchronous support (*note Background
        Execution::) of GDB.

        Remote asynchronous support will be disabled until you use the
        `maint set remote-async' command to enable it.


`set target-async' is mentioned but not described as a boolean command.

The manual says:

                                           The MI execution commands (*note
    GDB/MI Program Execution::) are always executed asynchronously in
   non-stop mode.

That does not appear to be true.  It seems that you need to set target-async
in this case too.

Many MI commands accept the options "--thread" and "--frame" now but I can see
no mention of this in the manual.

The MI commands "-exec-interrupt" and "-exec-continue" accept "--all" and this
is not mentioned either.

In MI, the async record *stopped always generates a "stopped-threads" field
but this is neither described nor displayed any of the examples showing
*stopped output in the manual.

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

Re: Documentation issues

[Vladimir Prus]

Nick Roberts wrote:

> The manual says:
> 
>                                            The MI execution commands (*note
>     GDB/MI Program Execution::) are always executed asynchronously in
>    non-stop mode.

> That does not appear to be true.  It seems that you need to set target-async
> in this case too.

I don't think you can enable non-stop mode if async is not enabled, ever.

> Many MI commands accept the options "--thread" and "--frame" now but I can see
> no mention of this in the manual.
> 
> The MI commands "-exec-interrupt" and "-exec-continue" accept "--all" and this
> is not mentioned either.
> 
> In MI, the async record *stopped always generates a "stopped-threads" field
> but this is neither described nor displayed any of the examples showing
> *stopped output in the manual.

This all is in the works and will be submitted, together with a bunch of multi-process
MI changes, next week.

- Volodya

Re: Documentation issues

[Nick Roberts]

On Sun, 02 Nov 2008, Vladimir Prus writes:
 > Nick Roberts wrote:
 > 
 > > The manual says:
 > > 
 > >                                            The MI execution commands (*note
 > >     GDB/MI Program Execution::) are always executed asynchronously in
 > >    non-stop mode.
 > 
 > > That does not appear to be true.  It seems that you need to set target-async
 > > in this case too.
 > 
 > I don't think you can enable non-stop mode if async is not enabled, ever.

When I try it, it looks to me like you can:

nickrob@kahikatea:~$ src-clean/gdb/gdb myprog
GNU gdb (GDB) 6.8.50.20081215-cvs
...
(gdb) set non-stop on
(gdb) show non-stop
Controlling the inferior in non-stop mode is on.
(gdb) show target-async
Controlling the inferior in asynchronous mode is off.

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