From: Stan Shebs <stan@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stan Shebs <stan@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Document tracepoint restrictions
Date: Fri, 12 Mar 2010 18:51:00 -0000 [thread overview]
Message-ID: <4B9A8D39.6030302@codesourcery.com> (raw)
In-Reply-To: <83ociu0x9l.fsf@gnu.org>
Eli Zaretskii wrote:
>> + bytes from the stack pointer with something like @code{*$esp@@300}
>> + (adjust to use the name of the actual stack pointer register on your
>> + target architecture, and the amount of stack you wish to capture).
>>
>
> Isn't it better to just use the generic $sp here? Or are you saying
> that it is not supported by tracepoints?
>
$sp is a pseudo-register, and garners a complaint right now.
> Okay with these changes.
>
Thanks, I'll make the fixes!
Stan
prev parent reply other threads:[~2010-03-12 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 2:40 Stan Shebs
2010-03-12 8:17 ` Eli Zaretskii
2010-03-12 18:51 ` Stan Shebs [this message]
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=4B9A8D39.6030302@codesourcery.com \
--to=stan@codesourcery.com \
--cc=eliz@gnu.org \
--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