Subversion Repositories or1k

This is ./gdb.info, produced by Makeinfo version 3.12f from gdb.texinfo.

INFO-DIR-SECTION Programming & development tools.

START-INFO-DIR-ENTRY

* Gdb: (gdb).                     The GNU debugger.

END-INFO-DIR-ENTRY

   This file documents the GNU debugger GDB.

   This is the Eighth Edition, March 2000, of `Debugging with GDB: the

GNU Source-Level Debugger' for GDB Version 5.0.

   Copyright (C) 1988-2000 Free Software Foundation, Inc.

   Permission is granted to make and distribute verbatim copies of this

manual provided the copyright notice and this permission notice are

preserved on all copies.

   Permission is granted to copy and distribute modified versions of

this manual under the conditions for verbatim copying, provided also

that the entire resulting derived work is distributed under the terms

of a permission notice identical to this one.

   Permission is granted to copy and distribute translations of this

manual into another language, under the above conditions for modified

versions.

File: gdb.info,  Node: GDB/MI Result Records,  Next: GDB/MI Stream Records,  Up: GDB/MI Output Records

GDB/MI Result Records

---------------------

   In addition to a number of out-of-band notifications, the response

to a GDB/MI command includes one of the following result indications:

`"^done" [ "," RESULTS ]'

     The synchronous operation was successful, `RESULTS' is the return

     value.

`"^running"'

     The asynchronous operation was successfully started.  The target is

     running.

`"^error" "," C-STRING'

     The operation failed.  The `C-STRING' contains the corresponding

     error message.

File: gdb.info,  Node: GDB/MI Stream Records,  Next: GDB/MI Out-of-band Records,  Prev: GDB/MI Result Records,  Up: GDB/MI Output Records

GDB/MI Stream Records

---------------------

   GDB internally maintains a number of output streams: the console, the

target, and the log.  The output intended for each of these streams is

funneled through the GDB/MI interface using "stream records".

   Each stream record begins with a unique "prefix character" which

identifies its stream (*note GDB/MI Output Syntax: GDB/MI Output

Syntax.). In addition to the prefix, each stream record contains a

`STRING-OUTPUT'.  This is either raw text (with an implicit new line)

or a quoted C string (which does not contain an implicit newline).

`"~" STRING-OUTPUT'

     The console output stream contains text that should be displayed

     in the CLI console window.  It contains the textual responses to

     CLI commands.

`"@" STRING-OUTPUT'

     The target output stream contains any textual output from the

     running target.

`"&" STRING-OUTPUT'

     The LOG stream contains debugging messages being produced by GDB's

     internals.

File: gdb.info,  Node: GDB/MI Out-of-band Records,  Prev: GDB/MI Stream Records,  Up: GDB/MI Output Records

GDB/MI Out-of-band Records

--------------------------

   "Out-of-band" records are used to notify the GDB/MI client of

additional changes that have occurred.  Those changes can either be a

consequence of GDB/MI (e.g., a breakpoint modified) or a result of

target activity (e.g., target stopped).

   The following is a preliminary list of possible out-of-band records.

`"*" "stop"'

File: gdb.info,  Node: GDB/MI Command Description Format,  Next: GDB/MI Breakpoint Table Commands,  Prev: GDB/MI Output Records,  Up: GDB/MI

GDB/MI Command Description Format

=================================

   The remaining sections describe blocks of commands.  Each block of

commands is laid out in a fashion similar to this chapter.

   Note the the line breaks shown in the examples are here only for

readability. They don't appear in the real output.  Also note that the

commands with a non-available example (N.A.) are not yet implemented.

Motivation

----------

   The motivation for this collection of commands

Introduction

------------

   A brief introduction to this collection of commands as a whole.

Commands

--------

   For each command in the block, the following is described:

Synopsis

........

      -command ARGS...

GDB Command

...........

   The corresponding GDB CLI command.

Result

......

Out-of-band

...........

Notes

.....

Example

.......

File: gdb.info,  Node: GDB/MI Breakpoint Table Commands,  Next: GDB/MI Data Manipulation,  Prev: GDB/MI Command Description Format,  Up: GDB/MI

GDB/MI Breakpoint table commands

================================

   This section documents GDB/MI commands for manipulating breakpoints.

The `-break-after' Command

--------------------------

Synopsis

........

      -break-after NUMBER COUNT

   The breakpoint number NUMBER is not in effect until it has been hit

COUNT times.  To see how this is reflected in the output of the

`-break-list' command, see the description of the `-break-list' command

below.

GDB Command

...........

   The corresponding GDB command is `ignore'.

Example

.......

     (gdb)

     -break-insert main

     ^done,bkpt={number="1",addr="0x000100d0",file="hello.c",line="5"}

     (gdb)

     -break-after 1 3

     ~

     ^done

     (gdb)

     -break-list

     ^done,BreakpointTable={hdr={"Num","Type","Disp","Enb","Address","What"},

     bkpt={number="1",type="breakpoint",disp="keep",enabled="y",

     addr="0x000100d0",func="main",file="hello.c",line="5",times="0",

     ignore="3"}}

     (gdb)

-break-condition

----------------

Synopsis

........

      -break-condition NUMBER EXPR

   Breakpoint NUMBER will stop the program only if the condition in

EXPR is true.  The condition becomes part of the `-break-list' output

(see the description of the `-break-list' command below).

GDB Command

...........

   The corresponding GDB command is `condition'.

Example

.......

     (gdb)

     -break-condition 1 1

     ^done

     (gdb)

     -break-list

     ^done,BreakpointTable={hdr={"Num","Type","Disp","Enb","Address","What"},

     bkpt={number="1",type="breakpoint",disp="keep",enabled="y",

     addr="0x000100d0",func="main",file="hello.c",line="5",cond="1",

     times="0",ignore="3"}}

     (gdb)

The `-break-delete' Command

---------------------------

Synopsis

........

      -break-delete ( BREAKPOINT )+

   Delete the breakpoint(s) whose number(s) are specified in the

argument list. This is obviously reflected in the breakpoint list.

GDB command

...........

   The corresponding GDB command is `delete'.

Example

.......

     (gdb)

     -break-delete 1

     ^done

     (gdb)

     -break-list

     ^done,BreakpointTable={}

     (gdb)

The `-break-disable' Command

----------------------------

Synopsis

........

      -break-disable ( BREAKPOINT )+

   Disable the named BREAKPOINT(s).  The field `enabled' in the break

list is now set to `n' for the named BREAKPOINT(s).

GDB Command

...........

   The corresponding GDB command is `disable'.

Example

.......

     (gdb)

     -break-disable 2

     ^done

     (gdb)

     -break-list

     ^done,BreakpointTable={hdr={"Num","Type","Disp","Enb","Address","What"},

     bkpt={number="2",type="breakpoint",disp="keep",enabled="n",

     addr="0x000100d0",func="main",file="hello.c",line="5",times="0"}}

     (gdb)

The `-break-enable' Command

---------------------------

Synopsis

........

      -break-enable ( BREAKPOINT )+

   Enable (previously disabled) BREAKPOINT(s).

GDB Command

...........

   The corresponding GDB command is `enable'.

Example

.......

     (gdb)

     -break-enable 2

     ^done

     (gdb)

     -break-list

     ^done,BreakpointTable={hdr={"Num","Type","Disp","Enb","Address","What"},

     bkpt={number="2",type="breakpoint",disp="keep",enabled="y",

     addr="0x000100d0",func="main",file="hello.c",line="5",times="0"}}

     (gdb)

The `-break-info' Command

-------------------------

Synopsis

........

      -break-info BREAKPOINT

   Get information about a single breakpoint.

GDB command

...........

   The corresponding GDB command is `info break BREAKPOINT'.

Example

.......

   N.A.

The `-break-insert' Command

---------------------------

Synopsis

........

      -break-insert [ -t ] [ -h ] [ -r ]

         [ -c CONDITION ] [ -i IGNORE-COUNT ]

         [ -p THREAD ] [ LINE | ADDR ]

If specified, LINE, can be one of:

   * function

   * filename:linenum

   * filename:function

   * *address

   The possible optional parameters of this command are:

`-t'

     Insert a tempoary breakpoint.

`-h'

     Insert a hardware breakpoint.

`-c CONDITION'

     Make the breakpoint conditional on CONDITION.

`-i IGNORE-COUNT'

     Initialize the IGNORE-COUNT.

`-r'

     Insert a regular breakpoint in all the functions whose names match

     the given regular expression.  Other flags are not applicable to

     regular expresson.

Result

......

   The result is in the form:

      ^done,bkptno="NUMBER",func="FUNCNAME",

       file="FILENAME",line="LINENO"

where NUMBER is the GDB number for this breakpoint, FUNCNAME is the

name of the function where the breakpoint was inserted, FILENAME is the

name of the source file which contains this function, and LINENO is the

source line number within that file.

   Note: this format is open to change.

GDB Command

...........

   The corresponding GDB commands are `break', `tbreak', `hbreak',

`thbreak', and `rbreak'.

Example

.......

     (gdb)

     -break-insert main

     ^done,bkpt={number="1",addr="0x0001072c",file="recursive2.c",line="4"}

     (gdb)

     -break-insert -t foo

     ^done,bkpt={number="2",addr="0x00010774",file="recursive2.c",line="11"}

     (gdb)

     -break-list

     ^done,BreakpointTable={hdr={"Num","Type","Disp","Enb","Address","What"},

     bkpt={number="1",type="breakpoint",disp="keep",enabled="y",

     addr="0x0001072c", func="main",file="recursive2.c",line="4",times="0"},

     bkpt={number="2",type="breakpoint",disp="del",enabled="y",

     addr="0x00010774",func="foo",file="recursive2.c",line="11",times="0"}}

     (gdb)

     -break-insert -r foo.*

     ~int foo(int, int);

     ^done,bkpt={number="3",addr="0x00010774",file="recursive2.c",line="11"}

     (gdb)

The `-break-list' Command

-------------------------

Synopsis

........

      -break-list

   Displays the list of inserted breakpoints, showing the following

fields:

`Number'

     number of the breakpoint

`Type'

     type of the breakpoint: `breakpoint' or `watchpoint'

`Disposition'

     should the breakpoint be deleted or disabled when it is hit: `keep'

     or `nokeep'

`Enabled'

     is the breakpoint enabled or no: `y' or `n'

`Address'

     memory location at which the breakpoint is set

`What'

     logical location of the breakpoint, expressed by function name,

     file name, line number

`times'

     number of times the breakpoint has been hit

   If there are no breakpoints or watchpoints, the BreakpointTable

field is an empty list.

GDB Command

...........

   The corresponding GDB command is `info break'.

Example

.......

     (gdb)

     -break-list

     ^done,BreakpointTable={hdr={"Num","Type","Disp","Enb","Address","What"},

     bkpt={number="1",type="breakpoint",disp="keep",enabled="y",

     addr="0x000100d0",func="main",file="hello.c",line="5",times="0"},

     bkpt={number="2",type="breakpoint",disp="keep",enabled="y",

     addr="0x00010114",func="foo",file="hello.c",line="13",times="0"}}

     (gdb)

   Here's an example of the result when there are no breakpoints:

     (gdb)

     -break-list

     ^done,BreakpointTable={}

     (gdb)

The `-break-watch' Command

--------------------------

Synopsis

........

      -break-watch [ -a | -r ]

   Create a watchpoint.  With the `-a' option it will create an

"access" watchpoint, i.e. a watchpoint that triggers either on a read

from or on a write to the memory location.  With the `-r' option, the

watchpoint created is a "read" watchpoint, i.e. it will trigger only

when the memory location is accessed for reading.  Without either of

the options, the watchpoint created is a regular watchpoint, i.e. it

will trigger when the memory location is accessed for writing.  *Note

Setting watchpoints: Set Watchpoints.

   Note that `-break-list' will report a single list of watchpoints and

breakpoints inserted.

GDB Command

...........

   The corresponding GDB commands are `watch', `awatch', and `rwatch'.

Example

.......

   Setting a watchpoint on a variable in the `main' function:

     (gdb)

     -break-watch x

     ^done,wpt={number="2",exp="x"}

     (gdb)

     -exec-continue

     ^running

     ^done,reason="watchpoint-trigger",wpt={number="2",exp="x"},

     value={old="-268439212",new="55"},

     frame={func="main",args={},file="recursive2.c",line="5"}

     (gdb)

   Setting a watchpoint on a variable local to a function.  GDB will

stop the program execution twice: first for the variable changing

value, then for the watchpoint going out of scope.

     (gdb)

     -break-watch C

     ^done,wpt={number="5",exp="C"}

     (gdb)

     -exec-continue

     ^running

     ^done,reason="watchpoint-trigger",

     wpt={number="5",exp="C"},value={old="-276895068",new="3"},

     frame={func="callee4",args={},

     file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="13"}

     (gdb)

     -exec-continue

     ^running

     ^done,reason="watchpoint-scope",wpnum="5",

     frame={func="callee3",args={{name="strarg",

     value="0x11940 \"A string argument.\""}},

     file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="18"}

     (gdb)

   Listing breakpoints and watchpoints, at different points in the

program execution.  Note that once the watchpoint goes out of scope, it

is deleted.

     (gdb)

     -break-watch C

     ^done,wpt={number="2",exp="C"}

     (gdb)

     -break-list

     ^done,BreakpointTable={hdr={"Num","Type","Disp","Enb","Address","What"},

     bkpt={number="1",type="breakpoint",disp="keep",enabled="y",

     addr="0x00010734",func="callee4",

     file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8",times="1"},

     bkpt={number="2",type="watchpoint",disp="keep",

     enabled="y",addr="",what="C",times="0"}}

     (gdb)

     -exec-continue

     ^running

     ^done,reason="watchpoint-trigger",wpt={number="2",exp="C"},

     value={old="-276895068",new="3"},

     frame={func="callee4",args={},

     file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="13"}

     (gdb)

     -break-list

     ^done,BreakpointTable={hdr={"Num","Type","Disp","Enb","Address","What"},

     bkpt={number="1",type="breakpoint",disp="keep",enabled="y",

     addr="0x00010734",func="callee4",

     file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8",times="1"},

     bkpt={number="2",type="watchpoint",disp="keep",

     enabled="y",addr="",what="C",times="-5"}}

     (gdb)

     -exec-continue

     ^running

     ^done,reason="watchpoint-scope",wpnum="2",

     frame={func="callee3",args={{name="strarg",

     value="0x11940 \"A string argument.\""}},

     file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="18"}

     (gdb)

     -break-list

     ^done,BreakpointTable={hdr={"Num","Type","Disp","Enb","Address","What"},

     bkpt={number="1",type="breakpoint",disp="keep",enabled="y",

     addr="0x00010734",func="callee4",

     file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8",times="1"}}

     (gdb)

File: gdb.info,  Node: GDB/MI Data Manipulation,  Next: GDB/MI Program Control,  Prev: GDB/MI Breakpoint Table Commands,  Up: GDB/MI

GDB/MI Data Manipulation

========================

   This section describes the GDB/MI commands that manipulate data:

examine memory and registers, evaluate expressions, etc.

The `-data-disassemble' Command

-------------------------------

Synopsis

........

      -data-disassemble

         [ -s START-ADDR -e END-ADDR ]

       | [ -f FILENAME -l LINENUM [ -n LINES ] ]

       -- MODE

Where:

`START-ADDR'

     is the beginning address (or `$pc')

`END-ADDR'

     is the end address

`FILENAME'

     is the name of the file to disassemble

`LINENUM'

     is the line number to disassemble around

`LINES'

     is the the number of disassembly lines to be produced.  If it is

     -1, the whole function will be disassembled, in case no END-ADDR is

     specified.  If END-ADDR is specified as a non-zero value, and

     LINES is lower than the number of disassembly lines between

     START-ADDR and END-ADDR, only LINES lines are displayed; if LINES

     is higher than the number of lines between START-ADDR and

     END-ADDR, only the lines up to END-ADDR are displayed.

`MODE'

     is either 0 (meaning only disassembly) or 1 (meaning mixed source

     and disassembly)

Result

......

   The output for each instruction is composed of two fields:

   * Address

   * Func-name

   * Offset

   * Instruction

   Note that whatever included in the instruction field, is not

manipulated directely by flathead, i.e. it is not possible to adjust

its format.

GDB Command

...........

   There's no direct mapping from this command to the CLI.

Example

.......

   Disassemble from the current value of `$pc' to `$pc + 20':

     (gdb)

     -data-disassemble -s $pc -e "$pc + 20" -- 0

     ^done,

     asm_insns={

     {address="0x000107c0",func-name="main",offset="4",

     inst="mov  2, %o0"},

     {address="0x000107c4",func-name="main",offset="8",

     inst="sethi  %hi(0x11800), %o2"},

     {address="0x000107c8",func-name="main",offset="12",

     inst="or  %o2, 0x140, %o1\t! 0x11940 <_lib_version+8>"},

     {address="0x000107cc",func-name="main",offset="16",

     inst="sethi  %hi(0x11800), %o2"},

     {address="0x000107d0",func-name="main",offset="20",

     inst="or  %o2, 0x168, %o4\t! 0x11968 <_lib_version+48>"}}

     (gdb)

   Disassemble the whole `main' function.  Line 32 is part of `main'.

     -data-disassemble -f basics.c -l 32 -- 0

     ^done,asm_insns={

     {address="0x000107bc",func-name="main",offset="0",

     inst="save  %sp, -112, %sp"},

     {address="0x000107c0",func-name="main",offset="4",

     inst="mov   2, %o0"},

     {address="0x000107c4",func-name="main",offset="8",

     inst="sethi %hi(0x11800), %o2"},

     [...]

     {address="0x0001081c",func-name="main",offset="96",inst="ret "},

     {address="0x00010820",func-name="main",offset="100",inst="restore "}}

     (gdb)

   Disassemble 3 instructions from the start of `main':

     (gdb)

     -data-disassemble -f basics.c -l 32 -n 3 -- 0

     ^done,asm_insns={

     {address="0x000107bc",func-name="main",offset="0",

     inst="save  %sp, -112, %sp"},

     {address="0x000107c0",func-name="main",offset="4",

     inst="mov  2, %o0"},

     {address="0x000107c4",func-name="main",offset="8",

     inst="sethi  %hi(0x11800), %o2"}}

     (gdb)

   Disassemble 3 instructions from the start of `main' in mixed mode:

     (gdb)

     -data-disassemble -f basics.c -l 32 -n 3 -- 1

     ^done,asm_insns={

     src_and_asm_line={line="31",

     file="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb/ \

       testsuite/gdb.mi/basics.c",line_asm_insn={

     {address="0x000107bc",func-name="main",offset="0",

     inst="save  %sp, -112, %sp"}}},

     src_and_asm_line={line="32",

     file="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb/ \

       testsuite/gdb.mi/basics.c",line_asm_insn={

     {address="0x000107c0",func-name="main",offset="4",

     inst="mov  2, %o0"},

     {address="0x000107c4",func-name="main",offset="8",

     inst="sethi  %hi(0x11800), %o2"}}}}

     (gdb)

The `-data-evaluate-expression' Command

---------------------------------------

Synopsis

........

      -data-evaluate-expression EXPR

   Evaluate EXPR as an expression.  The expression could contain an

inferior function call.  The function call will execute synchronously.

If the expression contains spaces, it must be enclosed in double quotes.

GDB Command

...........

   The corresponding GDB commands are `print', `output', and `call'.

In `gdbtk' only, there's a corresponding `gdb_eval' command.

Example

.......

   In the following example, the numbers that precede the commands are

the "tokens" described in *Note GDB/MI Command Syntax: GDB/MI Command

Syntax.  Notice how GDB/MI returns the same tokens in its output.

     211-data-evaluate-expression A

     211^done,value="1"

     (gdb)

     311-data-evaluate-expression &A

     311^done,value="0xefffeb7c"

     (gdb)

     411-data-evaluate-expression A+3

     411^done,value="4"

     (gdb)

     511-data-evaluate-expression "A + 3"

     511^done,value="4"

     (gdb)

The `-data-list-changed-registers' Command

------------------------------------------

Synopsis

........

      -data-list-changed-registers

   Display a list of the registers that have changed.

GDB Command

...........

   GDB doesn't have a direct analog for this command; `gdbtk' has the

corresponding command `gdb_changed_register_list'.

Example

.......

   On a PPC MBX board:

     (gdb)

     -exec-continue

     ^running

     (gdb)

     *stopped,reason="breakpoint-hit",bkptno="1",frame={func="main",

     args={},file="try.c",line="5"}

     (gdb)

     -data-list-changed-registers

     ^done,changed-registers={"0","1","2","4","5","6","7","8","9",

     "10","11","13","14","15","16","17","18","19","20","21","22","23",

     "24","25","26","27","28","30","31","64","65","66","67","69"}

     (gdb)

The `-data-list-register-names' Command

---------------------------------------

Synopsis

........

      -data-list-register-names [ ( REGNO )+ ]

   Show a list of register names for the current target.  If no

arguments are given, it shows a list of the names of all the registers.

If integer numbers are given as arguments, it will print a list of the

names of the registers corresponding to the arguments.

GDB Command

...........

   GDB does not have a command which corresponds to

`-data-list-register-names'.  In `gdbtk' there is a corresponding

command `gdb_regnames'.

Example

.......

   For the PPC MBX board:

     (gdb)

     -data-list-register-names

     ^done,register-names={"r0","r1","r2","r3","r4","r5","r6","r7",

     "r8","r9","r10","r11","r12","r13","r14","r15","r16","r17","r18",

     "r19","r20","r21","r22","r23","r24","r25","r26","r27","r28","r29",

     "r30","r31","f0","f1","f2","f3","f4","f5","f6","f7","f8","f9",

     "f10","f11","f12","f13","f14","f15","f16","f17","f18","f19","f20",

     "f21","f22","f23","f24","f25","f26","f27","f28","f29","f30","f31",

     "pc","ps","cr","lr","ctr","xer"}

     (gdb)

     -data-list-register-names 1 2 3

     ^done,register-names={"r1","r2","r3"}

     (gdb)

The `-data-list-register-values' Command

----------------------------------------

Synopsis

........

      -data-list-register-values FMT [ ( REGNO )*]

   Display the registers' contents.  FMT is the format according to

which the registers' contents are to be returned, followed by an

optional list of numbers specifying the registers to display.  A

missing list of numbers indicates that the contents of all the

registers must be returned.

   Allowed formats for FMT are:

`x'

     Hexadecimal

`o'

     Octal

`t'

     Binary

`d'

     Decimal

`r'

     Raw

`N'

     Natural

GDB Command

...........

   The corresponding GDB commands are `info reg', `info all-reg', and

(in `gdbtk') `gdb_fetch_registers'.

Example

.......

   For a PPC MBX board (note: line breaks are for readability only, they

don't appear in the actual output):

     (gdb)

     -data-list-register-values r 64 65

     ^done,register-values={{number="64",value="0xfe00a300"},

     {number="65",value="0x00029002"}}

     (gdb)

     -data-list-register-values x

     ^done,register-values={{number="0",value="0xfe0043c8"},

     {number="1",value="0x3fff88"},{number="2",value="0xfffffffe"},

     {number="3",value="0x0"},{number="4",value="0xa"},

     {number="5",value="0x3fff68"},{number="6",value="0x3fff58"},

     {number="7",value="0xfe011e98"},{number="8",value="0x2"},

     {number="9",value="0xfa202820"},{number="10",value="0xfa202808"},

     {number="11",value="0x1"},{number="12",value="0x0"},

     {number="13",value="0x4544"},{number="14",value="0xffdfffff"},

     {number="15",value="0xffffffff"},{number="16",value="0xfffffeff"},

     {number="17",value="0xefffffed"},{number="18",value="0xfffffffe"},

     {number="19",value="0xffffffff"},{number="20",value="0xffffffff"},

     {number="21",value="0xffffffff"},{number="22",value="0xfffffff7"},

     {number="23",value="0xffffffff"},{number="24",value="0xffffffff"},

     {number="25",value="0xffffffff"},{number="26",value="0xfffffffb"},

     {number="27",value="0xffffffff"},{number="28",value="0xf7bfffff"},

     {number="29",value="0x0"},{number="30",value="0xfe010000"},

     {number="31",value="0x0"},{number="32",value="0x0"},

     {number="33",value="0x0"},{number="34",value="0x0"},

     {number="35",value="0x0"},{number="36",value="0x0"},

     {number="37",value="0x0"},{number="38",value="0x0"},

     {number="39",value="0x0"},{number="40",value="0x0"},

     {number="41",value="0x0"},{number="42",value="0x0"},

     {number="43",value="0x0"},{number="44",value="0x0"},

     {number="45",value="0x0"},{number="46",value="0x0"},

     {number="47",value="0x0"},{number="48",value="0x0"},

     {number="49",value="0x0"},{number="50",value="0x0"},

     {number="51",value="0x0"},{number="52",value="0x0"},

     {number="53",value="0x0"},{number="54",value="0x0"},

     {number="55",value="0x0"},{number="56",value="0x0"},

     {number="57",value="0x0"},{number="58",value="0x0"},

     {number="59",value="0x0"},{number="60",value="0x0"},

     {number="61",value="0x0"},{number="62",value="0x0"},

     {number="63",value="0x0"},{number="64",value="0xfe00a300"},

     {number="65",value="0x29002"},{number="66",value="0x202f04b5"},

     {number="67",value="0xfe0043b0"},{number="68",value="0xfe00b3e4"},

     {number="69",value="0x20002b03"}}

     (gdb)

The `-data-read-memory' Command

-------------------------------

Synopsis

........

      -data-read-memory [ -o BYTE-OFFSET ]

        ADDRESS WORD-FORMAT WORD-SIZE

        NR-ROWS NR-COLS [ ASCHAR ]

where:

`ADDRESS'

     An expression specifying the address of the first memory word to be

     read.  Complex expressions containing embedded white space should

     be quoted using the C convention.

`WORD-FORMAT'

     The format to be used to print the memory words.  The notation is

     the same as for GDB's `print' command (*note Output formats:

     Output Formats.).

`WORD-SIZE'

     The size of each memory word in bytes.

`NR-ROWS'

     The number of rows in the output table.