From: Hui Zhu <teawater@gmail.com>
To: gdb-patches ml <gdb-patches@sourceware.org>
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: [doc/tracepoint] Change *$esp@300 to *(unsigned char *)$esp@300.
Date: Fri, 16 Sep 2011 08:13:00 -0000 [thread overview]
Message-ID: <CANFwon3qCm9H8GY89d5MpiNkVwN=TCUhDA-6GWcqgiTs2dr6LQ@mail.gmail.com> (raw)
Hi,
I found that if want collect stack in tracepoint action like doc said
will got error.
collect $rsp@512
Left operand of `@' must be an object in memory.
But change to:
collect *(unsigned char *)$rsp@512
Will fix it.
So I make a patch for doc.
Please help me review it.
Thanks,
Hui
2011-09-16 Hui Zhu <teawater@gmail.com>
* gdb.texinfo (Tracepoint Restrictions): Change *$esp@300
to *(unsigned char *)$esp@300.
---
doc/gdb.texinfo | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/doc/gdb.texinfo
+++ b/doc/gdb.texinfo
@@ -10627,7 +10627,7 @@ by @code{ptr}.
@item
It is not possible to collect a complete stack backtrace at a
tracepoint. Instead, you may collect the registers and a few hundred
-bytes from the stack pointer with something like @code{*$esp@@300}
+bytes from the stack pointer with something like @code{*(unsigned
char *)$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).
Then the @code{backtrace} command will show a partial backtrace when
next reply other threads:[~2011-09-16 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 8:13 Hui Zhu [this message]
2011-09-16 8:57 ` Eli Zaretskii
2011-09-16 9:36 ` Hui Zhu
2011-09-16 10:45 ` 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='CANFwon3qCm9H8GY89d5MpiNkVwN=TCUhDA-6GWcqgiTs2dr6LQ@mail.gmail.com' \
--to=teawater@gmail.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