This is the mail archive of the
mailing list for the GDB project.
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: gdb at sourceware dot org
- Date: Sun, 2 Nov 2008 12:03:55 +1300
- Subject: Documentation issues
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
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.