mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2024-12-15 04:31:49 +08:00
2011-09-16 Hui Zhu <teawater@gmail.com>
* gdb.texinfo (Tracepoint Restrictions): Change *$esp@300 to *(unsigned char *)$esp@300.
This commit is contained in:
parent
63a9aad80e
commit
d99f7e4842
@ -1,3 +1,8 @@
|
||||
2011-09-16 Hui Zhu <teawater@gmail.com>
|
||||
|
||||
* gdb.texinfo (Tracepoint Restrictions): Change *$esp@300
|
||||
to *(unsigned char *)$esp@300.
|
||||
|
||||
2011-09-15 Paul Koning <paul_koning@dell.com>
|
||||
|
||||
* gdb.texinfo: Make style of Python functions and methods match
|
||||
|
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user