OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

* gdb.texinfo (Data): Link to pretty-printing. 

(Output Formats): Likewise.  Correct text.
This commit is contained in:
Tom Tromey 2010-03-05 20:01:21 +00:00
parent a6cc6b3bc4
commit 78e2826bcc
2 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/doc/ChangeLog
View File

@ -1,3 +1,8 @@
2010-03-05 Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Data): Link to pretty-printing.
(Output Formats): Likewise. Correct text.
2010-03-01 Daniel Jacobowitz <dan@codesourcery.com>
* gdb.texinfo (Types): Describe <struct> and <flags>.

9
gdb/doc/gdb.texinfo
View File

@ -6661,7 +6661,8 @@ The usual way to examine data in your program is with the @code{print}
command (abbreviated @code{p}), or its synonym @code{inspect}. It
evaluates and prints the value of an expression of the language your
program is written in (@pxref{Languages, ,Using @value{GDBN} with
Different Languages}).
Different Languages}). It may also print the expression using a
Python-based pretty-printer (@pxref{Pretty Printing}).
@table @code
@item print @var{expr}
@ -7159,8 +7160,10 @@ array.
@item r
@cindex raw printing
Print using the @samp{raw} formatting. By default, @value{GDBN} will
use a type-specific pretty-printer. The @samp{r} format bypasses any
pretty-printer which might exist for the value's type.
use a Python-based pretty-printer, if one is available (@pxref{Pretty
Printing}). This typically results in a higher-level display of the
value's contents. The @samp{r} format bypasses any Python
pretty-printer which might exist.
@end table
For example, to print the program counter in hex (@pxref{Registers}), type