This is the mail archive of the
mailing list for the GDB project.
Re: Documentation issues
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.