This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA 01/08] multi-process support: struct inferior


> 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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]