From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 01/08] multi-process support: struct inferior
Date: Fri, 12 Sep 2008 16:08:00 -0000 [thread overview]
Message-ID: <uiqt1pcsy.fsf@gnu.org> (raw)
In-Reply-To: <200809121637.34647.pedro@codesourcery.com>
> 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.
next prev parent reply other threads:[~2008-09-12 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 15:38 Pedro Alves
2008-09-12 16:08 ` Eli Zaretskii [this message]
2008-09-12 16:08 ` Eli Zaretskii
2008-09-12 17:21 ` Pedro Alves
2008-09-12 20:00 ` Eli Zaretskii
2008-09-16 22:05 ` Stan Shebs
2008-09-17 0:33 ` [RFA 01/08] multi-process support: struct inferior (alternate manual content) Stan Shebs
2008-09-17 3:17 ` Eli Zaretskii
2008-09-18 22:46 ` [RFA 01/08] multi-process support: struct inferior Daniel Jacobowitz
2008-09-22 15:35 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uiqt1pcsy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox