Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@mips.com>
To: Doug Evans <xdje42@gmail.com>, Phil Muldoon <pmuldoon@redhat.com>
Cc: <gdb@sourceware.org>
Subject: Documentation build regressions
Date: Wed, 30 May 2018 17:59:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1805301840590.10896@tp.orcam.me.uk> (raw)

Hi,

 I haven't run `make pdf' for a while and consequently I have only now 
noticed that it does not work anymore as TeX chokes on input.  I have 
tracked down the two offending commits to be:

commit e698b8c41cbb2648a11a2ae806922c44d1482aed
Author: Doug Evans <xdje42@gmail.com>
Date:   Tue Jun 3 00:29:49 2014 -0700

    Add command support for Guile.

for a failure in `guile.texi':

.../gdb/doc/guile.texi:1711: Unbalanced parentheses in @def.
@badparencount ...{Unbalanced parentheses in @def}
                                                  @global @parencount =0
@checkparencounts ...ount =0 @else @badparencount
                                                  @fi @ifnum @brackcount =0 ...

@printdefunline ...enalty 10002 @checkparencounts
                                                  @endgroup
l.1711 ...x? prefix@r{]} @r{[}#:doc doc-string{]})

?

and:

commit 824cc835aa9a4d585d955db4ab2a5dd4c17cc22c
Author: Phil Muldoon <pmuldoon@redhat.com>
Date:   Thu Dec 7 16:47:33 2017 +0000

    Implement explicit locations for Python breakpoints.

for a failure in `python.texi':

.../gdb/doc/python.texi:4881: Unbalanced square braces in @def.
@badbrackcount ...nbalanced square braces in @def}
                                                  @global @brackcount =0
@checkparencounts ...ount =0 @else @badbrackcount
                                                  @fi
@printdefunline ...enalty 10002 @checkparencounts
                                                  @endgroup
l.4881 ...n @r{]}, label @r{]}, line @r{]]]]]]]]})

?

The latter file and offending line has been modified since and still fails 
in a similar manner.  If I revert both files to just before the respective 
commits, then `make pdf' succeeds.  This is with:

This is pdfeTeXk, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)

You surely must have verified your changes before committing and the 
former one is especially old, so am I missing something?  I find it hard 
to believe nobody has tripped over it so far.

  Maciej


             reply	other threads:[~2018-05-30 17:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 17:59 Maciej W. Rozycki [this message]
2018-05-30 20:12 ` Tom Tromey
2018-05-30 20:56 ` Jan Kratochvil
2018-05-31 17:23 ` Joseph Myers
2018-06-01 14:01   ` Jan Kratochvil
2018-06-01 19:38     ` Joseph Myers
2018-06-04 20:27       ` Maciej W. Rozycki
2018-06-05  9:49         ` variable displayed twice when using GDB/MI Xavier Roirand
2018-06-07 11:33           ` Pedro Alves
2018-05-31 17:51 ` Documentation build regressions 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=alpine.DEB.2.00.1805301840590.10896@tp.orcam.me.uk \
    --to=macro@mips.com \
    --cc=gdb@sourceware.org \
    --cc=pmuldoon@redhat.com \
    --cc=xdje42@gmail.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