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: Tue, 24 Aug 2010 02:10:00 -0000 [thread overview]
Message-ID: <AANLkTin9QngDp-BZL15Fp2Qtaj1MWSa5Bvqy3=YnwO3t@mail.gmail.com> (raw)
Hi,
I found that *$esp@300 cannot work on GDB, for example:
actions
Enter actions for tracepoint 4, one per line.
End with a line saying just "end".
>collect *$esp@300
Attempt to dereference a generic pointer.
But *(unsigned char *)$esp@300 can work:
actions
Enter actions for tracepoint 4, one per line.
End with a line saying just "end".
>collect *(unsigned char *)$esp@300
>end
I make a patch for it. Please help me review it.
Thanks,
Hui
2010-08-24 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
@@ -10390,7 +10390,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:[~2010-08-24 2:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 2:10 Hui Zhu [this message]
2010-08-24 3:06 ` Eli Zaretskii
2010-08-24 3:30 ` Hui Zhu
2010-08-24 17:08 ` Eli Zaretskii
2010-08-24 17:35 ` Michael Snyder
2010-08-24 18:00 ` Eli Zaretskii
2010-08-24 18:07 ` Michael Snyder
2010-08-24 18:37 ` Pedro Alves
2010-08-24 17:33 ` Michael Snyder
2010-08-24 17:58 ` 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='AANLkTin9QngDp-BZL15Fp2Qtaj1MWSa5Bvqy3=YnwO3t@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