From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [doc] Remote protocol: undocumented return value for 'p' and 'g'
Date: Thu, 23 Dec 2010 20:30:00 -0000 [thread overview]
Message-ID: <83sjxoe0ac.fsf@gnu.org> (raw)
In-Reply-To: <201012231913.08466.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Thu, 23 Dec 2010 19:13:08 +0000
>
> It's intended usage is in the context of inspecting tracepoints, to
> report "the register exists, but I don't know its value, because I
> haven't collected it."
>
> (We actually have a local series of 60 or so (and counting)
> trace debugging related patches that actually make use of
> this mechanism).
>
> Okay to apply?
Yes, thanks.
> +literal @samp{x}'s in place of the register data digits, to indicate
> +the corresponding register has not been collected, thus its value is
"... to indicate that the corresponding register ..."
> +registers 0 and 2 have not been collected, while registers 1 and 3
> +have been collected, and have value zero each:
^^^^^^^^^^^^^^^^^^^^^^^^
"and both have zero value"
next prev parent reply other threads:[~2010-12-23 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 19:52 Pedro Alves
2010-12-23 20:30 ` Eli Zaretskii [this message]
2010-12-24 2:50 ` 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=83sjxoe0ac.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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