From 78e2826bcc9ddadf05c070c479a3f5e608654b16 Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Fri, 5 Mar 2010 20:01:21 +0000 Subject: [PATCH] * gdb.texinfo (Data): Link to pretty-printing. (Output Formats): Likewise. Correct text. --- gdb/doc/ChangeLog | 5 +++++ gdb/doc/gdb.texinfo | 9 ++++++--- 2 files changed, 11 insertions(+), 3 deletions(-) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index ab9437928a..2bd09a898a 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,8 @@ +2010-03-05 Tom Tromey + + * gdb.texinfo (Data): Link to pretty-printing. + (Output Formats): Likewise. Correct text. + 2010-03-01 Daniel Jacobowitz * gdb.texinfo (Types): Describe and . diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 6bb7d52125..6ea3a60e00 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -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