From: Stan Shebs <stanshebs@earthlink.net>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Justin Lebar <justin.lebar@gmail.com>, gdb-patches@sourceware.org
Subject: Re: Status of 'blacklist' patch?
Date: Wed, 02 Nov 2011 23:52:00 -0000 [thread overview]
Message-ID: <4EB1D7C2.8070704@earthlink.net> (raw)
In-Reply-To: <alpine.DEB.1.10.1111022229240.31737@tp.orcam.me.uk>
On 11/2/11 3:42 PM, Maciej W. Rozycki wrote:
> This change broke the build of gdb.info:
>
> makeinfo --css-ref=../cs.css --split-size=5000000 --split-size=5000000 --split-size=5000000 -DHAVE_MAKEINFO_CLICK -I .../gdb/doc/../../readline/doc -I .../gdb/doc/../mi -I .../gdb/doc \
> -o gdb.info .../gdb/doc/gdb.texinfo
> .../gdb/doc/gdb.texinfo:4899: warning: `.' or `,' must follow @xref, not `I'.
> .../gdb/doc/gdb.texinfo:4857: `Skipping Over Functions and Files' has no Up field(perhaps incorrect sectioning?).
> .../gdb/doc/gdb.texinfo:4857: warning: unreferenced node `Skipping Over Functionsand Files'.
> makeinfo: Removing output file `gdb.info' due to errors; use --force to preserve.
> make[5]: *** [gdb.info] Error 1
>
> Also a ChangeLog entry is missing for changes to gdb.texinfo -- please fix
> that up.
>
> OK to apply the fix for the build errors below?
Yes, this is good. (I just bumped into it myself...)
Stan
>
> 2011-11-02 Maciej W. Rozycki<macro@codesourcery.com>
>
> gdb/doc/
> * gdb.texinfo (Skipping Over Functions and Files): Remove node
> designation. Fix "Specify Location" cross-reference.
>
> Maciej
>
> gdb-info-fix.diff
> Index: gdb-fsf-trunk-quilt/gdb/doc/gdb.texinfo
> ===================================================================
> --- gdb-fsf-trunk-quilt.orig/gdb/doc/gdb.texinfo 2011-11-02 21:25:50.000000000 +0000
> +++ gdb-fsf-trunk-quilt/gdb/doc/gdb.texinfo 2011-11-02 22:22:53.495572496 +0000
> @@ -4854,7 +4854,6 @@ proceed until the function returns.
> An argument is a repeat count, as in @code{next}.
> @end table
>
> -@node Skipping Over Functions and Files
> @subsection Skipping Over Functions and Files
> @cindex skipping over functions and files
>
> @@ -4896,7 +4895,7 @@ example, @code{skip file boring.c}.
> @itemx skip function @r{[}@var{linespec}@r{]}
> After running this command, the function named by @var{linespec} or the
> function containing the line named by @var{linespec} will be skipped over when
> -stepping. @xref{Specify Location}
> +stepping. @xref{Specify Location}.
>
> If you do not specify @var{linespec}, the function you're currently debugging
> will be skipped.
>
next prev parent reply other threads:[~2011-11-02 23:52 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 12:12 Diego Novillo
2011-10-06 14:08 ` Justin Lebar
2011-10-06 15:51 ` Stan Shebs
2011-10-06 20:16 ` Justin Lebar
2011-10-10 12:34 ` Stan Shebs
2011-10-11 21:34 ` Justin Lebar
2011-10-11 23:54 ` Doug Evans
2011-10-16 19:22 ` Justin Lebar
2011-10-20 19:46 ` Tom Tromey
2011-10-25 20:07 ` Justin Lebar
2011-10-25 20:41 ` Pedro Alves
2011-10-25 21:25 ` Justin Lebar
2011-10-20 20:40 ` Eli Zaretskii
2011-10-25 16:47 ` Justin Lebar
2011-10-25 16:53 ` Eli Zaretskii
2011-10-25 19:52 ` Justin Lebar
2011-10-25 20:13 ` Eli Zaretskii
2011-10-25 20:30 ` Justin Lebar
2011-10-26 1:06 ` Stan Shebs
2011-10-26 3:45 ` Justin Lebar
2011-10-26 5:37 ` Stan Shebs
2011-10-26 8:10 ` Joel Brobecker
2011-10-26 13:28 ` Eli Zaretskii
2011-10-26 15:11 ` Justin Lebar
2011-10-28 18:18 ` Tom Tromey
2011-10-28 19:48 ` Justin Lebar
2011-10-28 19:53 ` Tom Tromey
2011-10-28 19:49 ` Tom Tromey
2011-10-28 19:55 ` Justin Lebar
2011-10-28 20:37 ` Tom Tromey
2011-10-31 15:52 ` Justin Lebar
[not found] ` <4EAF2E0E.7080508@earthlink.net>
2011-11-01 14:53 ` Justin Lebar
2011-11-02 22:43 ` Maciej W. Rozycki
2011-11-02 23:52 ` Stan Shebs [this message]
2011-11-03 0:20 ` Maciej W. Rozycki
2011-11-03 3:54 ` Eli Zaretskii
2011-11-03 14:32 ` Tom Tromey
2011-11-03 16:54 ` Eli Zaretskii
2011-11-03 18:04 ` Maciej W. Rozycki
2011-11-03 18:25 ` Eli Zaretskii
2011-11-03 19:01 ` Stan Shebs
2011-10-06 17:19 ` Diego Novillo
2011-10-06 17:33 ` Tom Tromey
2011-10-06 17:37 ` Diego Novillo
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=4EB1D7C2.8070704@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=gdb-patches@sourceware.org \
--cc=justin.lebar@gmail.com \
--cc=macro@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