From: Jonny Grant <jg@jguk.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: gdb online manuals
Date: Wed, 22 Jul 2020 23:28:40 +0100 [thread overview]
Message-ID: <cc8c9cb7-220a-a871-613e-840dce109616@jguk.org> (raw)
In-Reply-To: <20200715183937.GE5016@adacore.com>
On 15/07/2020 19:39, Joel Brobecker wrote:
>> Is the gdb version 9 manual online? I could only find the latest development version online from this page https://www.gnu.org/software/gdb/documentation/
>
> We are aware that the documentation page is a bit confusing and that
> it could use some love but unfortunately, it's tied to scripts
> that run nightly as well as the release process, and we're lacking
> resources to tackle that.
>
> In the meantime, the page you reference above has a line that points
> you to the documentation of the latest release:
> https://sourceware.org/gdb/download/onlinedocs/
>
> Incidentally, that page allows you to chose which you want to look at
> (at the top, you see links to "most recent branch" and "current").
>
Hello Joel
Thank you for the tip.
Ok, I saw version 9 is documented here now:
https://sourceware.org/gdb/onlinedocs/gdb/index.html
I noticed "refcard" and "stack_frame" only have gz versions. refcard.pdf.gz is actually only 1000 bytes smaller compressed, maybe simpler just to show it as a PDF? At least it shows in the browser then.
stack_frame.pdf.gz is 7000 bytes smaller. I'm sure the web-browser would download it via http compression anyway.
Thank you
Jonny
next prev parent reply other threads:[~2020-07-22 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 9:27 Jonny Grant
2020-07-15 18:39 ` Joel Brobecker
2020-07-22 22:28 ` Jonny Grant [this message]
2020-09-21 0:38 ` Joel Brobecker
2020-09-21 22:59 ` Jonny Grant
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=cc8c9cb7-220a-a871-613e-840dce109616@jguk.org \
--to=jg@jguk.org \
--cc=brobecker@adacore.com \
--cc=gdb@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).