From: Eli Zaretskii <eliz@gnu.org>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v5] Explicit locations: documentation updates
Date: Wed, 20 May 2015 15:49:00 -0000 [thread overview]
Message-ID: <838ucj6yg7.fsf@gnu.org> (raw)
In-Reply-To: <20150519221511.808.10790.stgit@valrhona.uglyboxes.com>
> From: Keith Seitz <keiths@redhat.com>
> Date: Tue, 19 May 2015 15:16:43 -0700
>
> This patch adds documentation for explicit locations to both the
> User Manual and gdb's online help system.
>
> gdb/ChangeLog:
>
> * NEWS: Mention explicit locations.
> * breakpoint.c [LOCATION_HELP_STRING]: New macro.
> [BREAK_ARGS_HELP]: Use LOCATION_HELP_STRING.
> (_initialize_breakpoint): Update documentation for
> "clear", "break", "trace", "strace", "ftrace", and "dprintf".
>
> gdb/doc/ChangeLog:
>
> * gdb.texinfo (Thread-Specific Breakpoints, Printing Source Lines):
> Use "location(s)"instead of "linespec(s)".
> (Specifying a Location): Rewrite.
> Add subsections describing linespec, address, and explicit locations.
> Add node/menu for each subsection.
> (Source and Machine Code, C Preprocessor Macros)
> (Create and Delete Trace points)
> (Extensions for Ada Tasks): Use "location(s)" instead of "linespec(s)".
> (Continuing at a Different Address): Remove "linespec" examples.
> Add reference to "Specify a Location"
> (The -break-insert Command): Rewrite. Add anchor.
> Add reference to appropriate manual section discussing locations.
> (The -dprintf-insert Command): Refer to -break-insert for
> specification of 'location'.
>
> This patch is originally #9/9.
>
> Differences from the last version:
>
> 1. Changed anchors to nodes for new subections.
> 2. Added new subsection menu to parent node, Specify Location.
> 3. Added @code as requested/necessary.
> 4. Updated ChangeLog
>
> [Eli, I know you pre-approved with fixes, but I'd appreciate one more
> look at this to double-check one more time.]
LGTM, with one comment:
> +@node Linespec Locations
> +@subsection Linespec Locations
Please add a @cindex entry here that's identical to the subsection
name, just without capitalization, like you did for the other 2
subsections you wrote.
Thanks.
next prev parent reply other threads:[~2015-05-20 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 22:16 Keith Seitz
2015-05-20 15:49 ` Eli Zaretskii [this message]
2015-05-20 16:03 ` Keith Seitz
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=838ucj6yg7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.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