2011-09-16 Hui Zhu <teawater@gmail.com>

	* gdb.texinfo (Tracepoint Restrictions): Change *$esp@300
	to *(unsigned char *)$esp@300.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index a513097..7d1e0d4 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -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

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 982843a..051377d 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/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