From: Will <gdb@korte.land>
To: gdb@sourceware.org
Subject: gdb cheat sheet
Date: Tue, 30 Jun 2015 10:31:00 -0000 [thread overview]
Message-ID: <56e80c7b38988179c57b4947e16bba78@mail.korte.land> (raw)
Hi everyone,
I'm really not sure where to send this, so here I am.
There exists, on the Internet, an excellent cheat sheet for gdb (I'll
link to it if asked - it's not on any site associated with gdb or the
FSF, so I'm not sure if I'm allowed to post the link). It is listed as
being copyright the Free Software Foundation, and is GPL-ed.
I can't find any mention of it anywhere on the gdb website, and I would
like the LaTeX source (it looks very LaTex-ish), as I'm not much good at
LaTeX and want to create an Emacs version. It's also missing a few
shorthands, which I'd like to add.
The cheat sheet also lists bug-gdb@gnu.org as a contact address, but
that looks like it is for more general bug reporting, and I haven't got
a reply yet.
Thanks,
- Will
next reply other threads:[~2015-06-30 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 10:31 Will [this message]
2015-06-30 12:40 ` Joel Brobecker
2015-07-02 5:01 ` Sergio Durigan Junior
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=56e80c7b38988179c57b4947e16bba78@mail.korte.land \
--to=gdb@korte.land \
--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