This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA 01/08] multi-process support: struct inferior
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pedro Alves <pedro at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 12 Sep 2008 19:08:16 +0300
- Subject: Re: [RFA 01/08] multi-process support: struct inferior
- References: <200809121637.34647.pedro@codesourcery.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Fri, 12 Sep 2008 16:37:34 +0100
>
> +@node Inferiors
> +@section Listing Inferiors
Some index entry should be here.
Also, I'm not sure this should be a top-level @section (but if it is,
I believe you will have to add it to the top-level menu as well). How
about making it a subsection of "Running"?
> +@value{GDBN} keeps track of the inferiors under control, be them
> +either running processes, core files, or remote targets without a
> +notion of processes, but which nonetheless have execution, and allows
> +the user to query and be notified about them uniformally, using the
> +commands below.
This text falls short of explaining why these features are useful.
Can we add something to explain this better?
> +The @code{set print inferior-events} command allows you to enable or
> +disable printing of messages when @value{GDBN} notices that new
> +inferiors have started or that inferiors have exited or have been
> +detached. By default, these messages will not be printed.
If the default is off, then perhaps we should tell when would the user
want them on. But maybe if you add explanation I asked for above,
they will clarify this as well.
Thanks.