public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "krab1991 at yahoo dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/11232] New: Table of contents is missing in DBG documentation (dvi, ps, pdf)
Date: Thu, 28 Jan 2010 07:53:00 -0000 [thread overview]
Message-ID: <20100128075326.11232.krab1991@yahoo.com> (raw)
Hi,
The "GDB User Manual" files given on the documentation page
http://sourceware.org/gdb/current/onlinedocs/
have empty section "Table of Contents" and section "Index".
But these are the most important sections for a 500-page document!
The bug appears in files:
http://sourceware.org/gdb/current/onlinedocs/gdb.pdf.gz
http://sourceware.org/gdb/current/onlinedocs/gdb.dvi.gz
http://sourceware.org/gdb/current/onlinedocs/gdb.ps.gz
Fix for this bug is pretty straightforward:
during compilation one needs to run TeXinfo three times, not only once.
This is a standard procedure in TeX to create Table of contents, indexing,
bibliography, cross-references, etc.
This bug was partially reported earlier (see Bug#: 10673 (gdb):
http://sourceware.org/bugzilla/show_bug.cgi?id=10673
"PDF version of GDB manual is missing table of contents" ).
Thanks.
--
Summary: Table of contents is missing in DBG documentation (dvi,
ps, pdf)
Product: gdb
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
AssignedTo: unassigned at sourceware dot org
ReportedBy: krab1991 at yahoo dot com
CC: gdb-prs at sourceware dot org
http://sourceware.org/bugzilla/show_bug.cgi?id=11232
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-01-28 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 7:53 krab1991 at yahoo dot com [this message]
2010-09-13 12:57 ` [Bug gdb/11232] " gaffa at users dot sf dot net
2010-09-13 13:05 ` gaffa at users dot sf dot net
2010-09-13 13:06 ` gaffa at users dot sf dot net
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=20100128075326.11232.krab1991@yahoo.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).