From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Hafiz_Abid@mentor.com, brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [patch] Change trace buffer size(v5)
Date: Mon, 11 Mar 2013 19:44:00 -0000 [thread overview]
Message-ID: <83zjy9k9h4.fsf@gnu.org> (raw)
In-Reply-To: <87txohn5wp.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: "Abid\, Hafiz" <Hafiz_Abid@mentor.com>, brobecker@adacore.com,
> gdb-patches@sourceware.org
> Date: Mon, 11 Mar 2013 12:32:54 -0600
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> Eli> Sorry, but this isn't right. You cannot have colons in @anchor or in
> Eli> @cindex entries, because that will confuse Info readers when they try
> Eli> to deduce the referenced spot.
>
> There are some other instances in gdb.texinfo:
>
> barimba. egrep '(anchor|cindex).*:' gdb.texinfo
> @cindex @code{::}, context for variables/functions
> @cindex @samp{qSearch:memory} packet
> @cindex <xi:include>
Thanks, fixed as below. (The other 2 places already had the
@ifnotinfo guards around these index entries.)
2013-03-11 Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo (General Query Packets): Don't use colon in index
entries visible to Info format.
Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.1059
diff -u -r1.1059 gdb.texinfo
--- gdb/doc/gdb.texinfo 11 Mar 2013 08:55:36 -0000 1.1059
+++ gdb/doc/gdb.texinfo 11 Mar 2013 19:43:00 -0000
@@ -37250,7 +37250,10 @@
@item qSearch:memory:@var{address};@var{length};@var{search-pattern}
@cindex searching memory, in remote debugging
+@ifnotinfo
@cindex @samp{qSearch:memory} packet
+@end ifnotinfo
+@cindex @samp{qSearch memory} packet
@anchor{qSearch memory}
Search @var{length} bytes at @var{address} for @var{search-pattern}.
@var{address} and @var{length} are encoded in hex.
prev parent reply other threads:[~2013-03-11 19:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 18:13 [patch] Change trace buffer size Abid, Hafiz
2013-02-18 20:00 ` Eli Zaretskii
2013-02-19 2:53 ` Yao Qi
2013-02-27 16:55 ` Pedro Alves
2013-02-28 0:52 ` Yao Qi
2013-02-27 16:39 ` Pedro Alves
2013-03-01 17:07 ` [patch] Change trace buffer size(v2) Abid, Hafiz
2013-03-01 18:13 ` zinteger setshow commands broken Pedro Alves
2013-03-04 10:10 ` Abid, Hafiz
2013-03-04 10:16 ` Yao Qi
2013-03-04 10:28 ` Pedro Alves
2013-03-01 20:02 ` [patch] Change trace buffer size(v2) Pedro Alves
2013-03-04 19:03 ` [patch] Change trace buffer size(v3) Abid, Hafiz
2013-03-04 20:43 ` Pedro Alves
2013-03-05 14:12 ` [patch] Change trace buffer size(v4) Abid, Hafiz
2013-03-05 20:13 ` Pedro Alves
2013-03-08 11:30 ` [patch] Change trace buffer size(v5) Abid, Hafiz
2013-03-08 14:09 ` Eli Zaretskii
2013-03-08 14:27 ` Abid, Hafiz
2013-03-08 14:28 ` Pedro Alves
2013-03-08 14:52 ` Yao Qi
2013-03-08 15:15 ` Abid, Hafiz
2013-03-08 15:27 ` Yao Qi
2013-05-02 17:31 ` Pedro Alves
2013-05-03 11:38 ` Abid, Hafiz
2013-05-03 14:05 ` Pedro Alves
2013-05-03 15:08 ` Abid, Hafiz
2013-05-03 15:26 ` Pedro Alves
2013-03-09 2:06 ` Joel Brobecker
2013-03-09 8:27 ` Eli Zaretskii
2013-03-09 10:20 ` Abid, Hafiz
2013-03-09 10:39 ` Abid, Hafiz
2013-03-09 11:11 ` Eli Zaretskii
2013-03-09 11:07 ` Eli Zaretskii
2013-03-11 18:33 ` Tom Tromey
2013-03-11 19:44 ` Eli Zaretskii [this message]
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=83zjy9k9h4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Hafiz_Abid@mentor.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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