From: Eli Zaretskii <eliz@gnu.org>
To: David Taylor <dtaylor@emc.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] doc of pre-defined or builtin trace state variables
Date: Thu, 12 Feb 2015 16:35:00 -0000 [thread overview]
Message-ID: <83fvab5bqw.fsf@gnu.org> (raw)
In-Reply-To: <2301.1423756145@usendtaylorx2l>
> From: David Taylor <dtaylor@emc.com>
> Date: Thu, 12 Feb 2015 10:49:05 -0500
>
> Our tracepoint users want certain capabilities for which 'pre-defined' or
> 'builtin' trace state variables seem like they would be a good fit. So,
> I started looking into what it would take to modify both GDB and our GDB
> stub to support them.
>
> Imagine my surprise to discover that GDB already supports them, but it
> is not documented!
>
> Here's a patch. The pdf, html, and info targets build without
> complaint. The modified paragraph in the pdf file looks okay.
>
> gdb/doc/ChangeLog:
>
> 2015-02-12 David Taylor <dtaylor@emc.com>
>
> * gdb.texinfo (Tracepoint Packets): Document the builtin and name
> fields of the QTDV packet.
Thanks, this is OK.
next prev parent reply other threads:[~2015-02-12 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 15:49 David Taylor
2015-02-12 16:35 ` Eli Zaretskii [this message]
2015-02-12 17:15 ` David Taylor
2015-02-12 20:41 ` Eli Zaretskii
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=83fvab5bqw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dtaylor@emc.com \
--cc=gdb-patches@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