<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
<html>
|
<!-- Copyright (C) 1988-2021 Free Software Foundation, Inc.
|
|
Permission is granted to copy, distribute and/or modify this document
|
under the terms of the GNU Free Documentation License, Version 1.3 or
|
any later version published by the Free Software Foundation; with the
|
Invariant Sections being "Free Software" and "Free Software Needs
|
Free Documentation", with the Front-Cover Texts being "A GNU Manual,"
|
and with the Back-Cover Texts as in (a) below.
|
|
(a) The FSF's Back-Cover Text is: "You are free to copy and modify
|
this GNU Manual. Buying copies from GNU Press supports the FSF in
|
developing GNU and promoting software freedom." -->
|
<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
|
<head>
|
<title>Debugging with GDB: GDB/MI Data Manipulation</title>
|
|
<meta name="description" content="Debugging with GDB: GDB/MI Data Manipulation">
|
<meta name="keywords" content="Debugging with GDB: GDB/MI Data Manipulation">
|
<meta name="resource-type" content="document">
|
<meta name="distribution" content="global">
|
<meta name="Generator" content="makeinfo">
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
<link href="index.html#Top" rel="start" title="Top">
|
<link href="Concept-Index.html#Concept-Index" rel="index" title="Concept Index">
|
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
|
<link href="GDB_002fMI.html#GDB_002fMI" rel="up" title="GDB/MI">
|
<link href="GDB_002fMI-Tracepoint-Commands.html#GDB_002fMI-Tracepoint-Commands" rel="next" title="GDB/MI Tracepoint Commands">
|
<link href="GDB_002fMI-Variable-Objects.html#GDB_002fMI-Variable-Objects" rel="previous" title="GDB/MI Variable Objects">
|
<style type="text/css">
|
<!--
|
a.summary-letter {text-decoration: none}
|
blockquote.smallquotation {font-size: smaller}
|
div.display {margin-left: 3.2em}
|
div.example {margin-left: 3.2em}
|
div.indentedblock {margin-left: 3.2em}
|
div.lisp {margin-left: 3.2em}
|
div.smalldisplay {margin-left: 3.2em}
|
div.smallexample {margin-left: 3.2em}
|
div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
|
div.smalllisp {margin-left: 3.2em}
|
kbd {font-style:oblique}
|
pre.display {font-family: inherit}
|
pre.format {font-family: inherit}
|
pre.menu-comment {font-family: serif}
|
pre.menu-preformatted {font-family: serif}
|
pre.smalldisplay {font-family: inherit; font-size: smaller}
|
pre.smallexample {font-size: smaller}
|
pre.smallformat {font-family: inherit; font-size: smaller}
|
pre.smalllisp {font-size: smaller}
|
span.nocodebreak {white-space:nowrap}
|
span.nolinebreak {white-space:nowrap}
|
span.roman {font-family:serif; font-weight:normal}
|
span.sansserif {font-family:sans-serif; font-weight:normal}
|
ul.no-bullet {list-style: none}
|
-->
|
</style>
|
|
|
</head>
|
|
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
|
<a name="GDB_002fMI-Data-Manipulation"></a>
|
<div class="header">
|
<p>
|
Next: <a href="GDB_002fMI-Tracepoint-Commands.html#GDB_002fMI-Tracepoint-Commands" accesskey="n" rel="next">GDB/MI Tracepoint Commands</a>, Previous: <a href="GDB_002fMI-Variable-Objects.html#GDB_002fMI-Variable-Objects" accesskey="p" rel="previous">GDB/MI Variable Objects</a>, Up: <a href="GDB_002fMI.html#GDB_002fMI" accesskey="u" rel="up">GDB/MI</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
|
</div>
|
<hr>
|
<a name="GDB_002fMI-Data-Manipulation-1"></a>
|
<h3 class="section">27.16 <small>GDB/MI</small> Data Manipulation</h3>
|
|
<a name="index-data-manipulation_002c-in-GDB_002fMI"></a>
|
<a name="index-GDB_002fMI_002c-data-manipulation"></a>
|
<p>This section describes the <small>GDB/MI</small> commands that manipulate data:
|
examine memory and registers, evaluate expressions, etc.
|
</p>
|
<p>For details about what an addressable memory unit is,
|
see <a href="Memory.html#addressable-memory-unit">addressable memory unit</a>.
|
</p>
|
|
<a name="The-_002ddata_002ddisassemble-Command"></a>
|
<h4 class="subheading">The <code>-data-disassemble</code> Command</h4>
|
<a name="index-_002ddata_002ddisassemble"></a>
|
|
<a name="Synopsis-64"></a>
|
<h4 class="subsubheading">Synopsis</h4>
|
|
<div class="smallexample">
|
<pre class="smallexample"> -data-disassemble
|
[ -s <var>start-addr</var> -e <var>end-addr</var> ]
|
| [ -a <var>addr</var> ]
|
| [ -f <var>filename</var> -l <var>linenum</var> [ -n <var>lines</var> ] ]
|
-- <var>mode</var>
|
</pre></div>
|
|
<p>Where:
|
</p>
|
<dl compact="compact">
|
<dt>‘<samp><var>start-addr</var></samp>’</dt>
|
<dd><p>is the beginning address (or <code>$pc</code>)
|
</p></dd>
|
<dt>‘<samp><var>end-addr</var></samp>’</dt>
|
<dd><p>is the end address
|
</p></dd>
|
<dt>‘<samp><var>addr</var></samp>’</dt>
|
<dd><p>is an address anywhere within (or the name of) the function to
|
disassemble. If an address is specified, the whole function
|
surrounding that address will be disassembled. If a name is
|
specified, the whole function with that name will be disassembled.
|
</p></dd>
|
<dt>‘<samp><var>filename</var></samp>’</dt>
|
<dd><p>is the name of the file to disassemble
|
</p></dd>
|
<dt>‘<samp><var>linenum</var></samp>’</dt>
|
<dd><p>is the line number to disassemble around
|
</p></dd>
|
<dt>‘<samp><var>lines</var></samp>’</dt>
|
<dd><p>is the number of disassembly lines to be produced. If it is -1,
|
the whole function will be disassembled, in case no <var>end-addr</var> is
|
specified. If <var>end-addr</var> is specified as a non-zero value, and
|
<var>lines</var> is lower than the number of disassembly lines between
|
<var>start-addr</var> and <var>end-addr</var>, only <var>lines</var> lines are
|
displayed; if <var>lines</var> is higher than the number of lines between
|
<var>start-addr</var> and <var>end-addr</var>, only the lines up to <var>end-addr</var>
|
are displayed.
|
</p></dd>
|
<dt>‘<samp><var>mode</var></samp>’</dt>
|
<dd><p>is one of:
|
</p><ul>
|
<li> 0 disassembly only
|
</li><li> 1 mixed source and disassembly (deprecated)
|
</li><li> 2 disassembly with raw opcodes
|
</li><li> 3 mixed source and disassembly with raw opcodes (deprecated)
|
</li><li> 4 mixed source and disassembly
|
</li><li> 5 mixed source and disassembly with raw opcodes
|
</li></ul>
|
|
<p>Modes 1 and 3 are deprecated. The output is “source centric”
|
which hasn’t proved useful in practice.
|
See <a href="Machine-Code.html#Machine-Code">Machine Code</a>, for a discussion of the difference between
|
<code>/m</code> and <code>/s</code> output of the <code>disassemble</code> command.
|
</p></dd>
|
</dl>
|
|
<a name="Result-6"></a>
|
<h4 class="subsubheading">Result</h4>
|
|
<p>The result of the <code>-data-disassemble</code> command will be a list named
|
‘<samp>asm_insns</samp>’, the contents of this list depend on the <var>mode</var>
|
used with the <code>-data-disassemble</code> command.
|
</p>
|
<p>For modes 0 and 2 the ‘<samp>asm_insns</samp>’ list contains tuples with the
|
following fields:
|
</p>
|
<dl compact="compact">
|
<dt><code>address</code></dt>
|
<dd><p>The address at which this instruction was disassembled.
|
</p>
|
</dd>
|
<dt><code>func-name</code></dt>
|
<dd><p>The name of the function this instruction is within.
|
</p>
|
</dd>
|
<dt><code>offset</code></dt>
|
<dd><p>The decimal offset in bytes from the start of ‘<samp>func-name</samp>’.
|
</p>
|
</dd>
|
<dt><code>inst</code></dt>
|
<dd><p>The text disassembly for this ‘<samp>address</samp>’.
|
</p>
|
</dd>
|
<dt><code>opcodes</code></dt>
|
<dd><p>This field is only present for modes 2, 3 and 5. This contains the raw opcode
|
bytes for the ‘<samp>inst</samp>’ field.
|
</p>
|
</dd>
|
</dl>
|
|
<p>For modes 1, 3, 4 and 5 the ‘<samp>asm_insns</samp>’ list contains tuples named
|
‘<samp>src_and_asm_line</samp>’, each of which has the following fields:
|
</p>
|
<dl compact="compact">
|
<dt><code>line</code></dt>
|
<dd><p>The line number within ‘<samp>file</samp>’.
|
</p>
|
</dd>
|
<dt><code>file</code></dt>
|
<dd><p>The file name from the compilation unit. This might be an absolute
|
file name or a relative file name depending on the compile command
|
used.
|
</p>
|
</dd>
|
<dt><code>fullname</code></dt>
|
<dd><p>Absolute file name of ‘<samp>file</samp>’. It is converted to a canonical form
|
using the source file search path
|
(see <a href="Source-Path.html#Source-Path">Specifying Source Directories</a>)
|
and after resolving all the symbolic links.
|
</p>
|
<p>If the source file is not found this field will contain the path as
|
present in the debug information.
|
</p>
|
</dd>
|
<dt><code>line_asm_insn</code></dt>
|
<dd><p>This is a list of tuples containing the disassembly for ‘<samp>line</samp>’ in
|
‘<samp>file</samp>’. The fields of each tuple are the same as for
|
<code>-data-disassemble</code> in <var>mode</var> 0 and 2, so ‘<samp>address</samp>’,
|
‘<samp>func-name</samp>’, ‘<samp>offset</samp>’, ‘<samp>inst</samp>’, and optionally
|
‘<samp>opcodes</samp>’.
|
</p>
|
</dd>
|
</dl>
|
|
<p>Note that whatever included in the ‘<samp>inst</samp>’ field, is not
|
manipulated directly by <small>GDB/MI</small>, i.e., it is not possible to
|
adjust its format.
|
</p>
|
<a name="GDB-Command-46"></a>
|
<h4 class="subsubheading"><small>GDB</small> Command</h4>
|
|
<p>The corresponding <small>GDB</small> command is ‘<samp>disassemble</samp>’.
|
</p>
|
<a name="Example-52"></a>
|
<h4 class="subsubheading">Example</h4>
|
|
<p>Disassemble from the current value of <code>$pc</code> to <code>$pc + 20</code>:
|
</p>
|
<div class="smallexample">
|
<pre class="smallexample">(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)
|
</pre></div>
|
|
<p>Disassemble the whole <code>main</code> function. Line 32 is part of
|
<code>main</code>.
|
</p>
|
<div class="smallexample">
|
<pre class="smallexample">-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)
|
</pre></div>
|
|
<p>Disassemble 3 instructions from the start of <code>main</code>:
|
</p>
|
<div class="smallexample">
|
<pre class="smallexample">(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)
|
</pre></div>
|
|
<p>Disassemble 3 instructions from the start of <code>main</code> in mixed mode:
|
</p>
|
<div class="smallexample">
|
<pre class="smallexample">(gdb)
|
-data-disassemble -f basics.c -l 32 -n 3 -- 1
|
^done,asm_insns=[
|
src_and_asm_line={line="31",
|
file="../../../src/gdb/testsuite/gdb.mi/basics.c",
|
fullname="/absolute/path/to/src/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="../../../src/gdb/testsuite/gdb.mi/basics.c",
|
fullname="/absolute/path/to/src/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)
|
</pre></div>
|
|
|
<a name="The-_002ddata_002devaluate_002dexpression-Command"></a>
|
<h4 class="subheading">The <code>-data-evaluate-expression</code> Command</h4>
|
<a name="index-_002ddata_002devaluate_002dexpression"></a>
|
|
<a name="Synopsis-65"></a>
|
<h4 class="subsubheading">Synopsis</h4>
|
|
<div class="smallexample">
|
<pre class="smallexample"> -data-evaluate-expression <var>expr</var>
|
</pre></div>
|
|
<p>Evaluate <var>expr</var> 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.
|
</p>
|
<a name="GDB-Command-47"></a>
|
<h4 class="subsubheading"><small>GDB</small> Command</h4>
|
|
<p>The corresponding <small>GDB</small> commands are ‘<samp>print</samp>’, ‘<samp>output</samp>’, and
|
‘<samp>call</samp>’. In <code>gdbtk</code> only, there’s a corresponding
|
‘<samp>gdb_eval</samp>’ command.
|
</p>
|
<a name="Example-53"></a>
|
<h4 class="subsubheading">Example</h4>
|
|
<p>In the following example, the numbers that precede the commands are the
|
<em>tokens</em> described in <a href="GDB_002fMI-Command-Syntax.html#GDB_002fMI-Command-Syntax"><small>GDB/MI</small>
|
Command Syntax</a>. Notice how <small>GDB/MI</small> returns the same tokens in its
|
output.
|
</p>
|
<div class="smallexample">
|
<pre class="smallexample">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)
|
</pre></div>
|
|
|
<a name="The-_002ddata_002dlist_002dchanged_002dregisters-Command"></a>
|
<h4 class="subheading">The <code>-data-list-changed-registers</code> Command</h4>
|
<a name="index-_002ddata_002dlist_002dchanged_002dregisters"></a>
|
|
<a name="Synopsis-66"></a>
|
<h4 class="subsubheading">Synopsis</h4>
|
|
<div class="smallexample">
|
<pre class="smallexample"> -data-list-changed-registers
|
</pre></div>
|
|
<p>Display a list of the registers that have changed.
|
</p>
|
<a name="GDB-Command-48"></a>
|
<h4 class="subsubheading"><small>GDB</small> Command</h4>
|
|
<p><small>GDB</small> doesn’t have a direct analog for this command; <code>gdbtk</code>
|
has the corresponding command ‘<samp>gdb_changed_register_list</samp>’.
|
</p>
|
<a name="Example-54"></a>
|
<h4 class="subsubheading">Example</h4>
|
|
<p>On a PPC MBX board:
|
</p>
|
<div class="smallexample">
|
<pre class="smallexample">(gdb)
|
-exec-continue
|
^running
|
|
(gdb)
|
*stopped,reason="breakpoint-hit",disp="keep",bkptno="1",frame={
|
func="main",args=[],file="try.c",fullname="/home/foo/bar/try.c",
|
line="5",arch="powerpc"}
|
(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)
|
</pre></div>
|
|
|
<a name="The-_002ddata_002dlist_002dregister_002dnames-Command"></a>
|
<h4 class="subheading">The <code>-data-list-register-names</code> Command</h4>
|
<a name="index-_002ddata_002dlist_002dregister_002dnames"></a>
|
|
<a name="Synopsis-67"></a>
|
<h4 class="subsubheading">Synopsis</h4>
|
|
<div class="smallexample">
|
<pre class="smallexample"> -data-list-register-names [ ( <var>regno</var> )+ ]
|
</pre></div>
|
|
<p>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. To ensure
|
consistency between a register name and its number, the output list may
|
include empty register names.
|
</p>
|
<a name="GDB-Command-49"></a>
|
<h4 class="subsubheading"><small>GDB</small> Command</h4>
|
|
<p><small>GDB</small> does not have a command which corresponds to
|
‘<samp>-data-list-register-names</samp>’. In <code>gdbtk</code> there is a
|
corresponding command ‘<samp>gdb_regnames</samp>’.
|
</p>
|
<a name="Example-55"></a>
|
<h4 class="subsubheading">Example</h4>
|
|
<p>For the PPC MBX board:
|
</p><div class="smallexample">
|
<pre class="smallexample">(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)
|
</pre></div>
|
|
<a name="The-_002ddata_002dlist_002dregister_002dvalues-Command"></a>
|
<h4 class="subheading">The <code>-data-list-register-values</code> Command</h4>
|
<a name="index-_002ddata_002dlist_002dregister_002dvalues"></a>
|
|
<a name="Synopsis-68"></a>
|
<h4 class="subsubheading">Synopsis</h4>
|
|
<div class="smallexample">
|
<pre class="smallexample"> -data-list-register-values
|
[ <code>--skip-unavailable</code> ] <var>fmt</var> [ ( <var>regno</var> )*]
|
</pre></div>
|
|
<p>Display the registers’ contents. The format according to which the
|
registers’ contents are to be returned is given by <var>fmt</var>, 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. The <code>--skip-unavailable</code> option
|
indicates that only the available registers are to be returned.
|
</p>
|
<p>Allowed formats for <var>fmt</var> are:
|
</p>
|
<dl compact="compact">
|
<dt><code>x</code></dt>
|
<dd><p>Hexadecimal
|
</p></dd>
|
<dt><code>o</code></dt>
|
<dd><p>Octal
|
</p></dd>
|
<dt><code>t</code></dt>
|
<dd><p>Binary
|
</p></dd>
|
<dt><code>d</code></dt>
|
<dd><p>Decimal
|
</p></dd>
|
<dt><code>r</code></dt>
|
<dd><p>Raw
|
</p></dd>
|
<dt><code>N</code></dt>
|
<dd><p>Natural
|
</p></dd>
|
</dl>
|
|
<a name="GDB-Command-50"></a>
|
<h4 class="subsubheading"><small>GDB</small> Command</h4>
|
|
<p>The corresponding <small>GDB</small> commands are ‘<samp>info reg</samp>’, ‘<samp>info
|
all-reg</samp>’, and (in <code>gdbtk</code>) ‘<samp>gdb_fetch_registers</samp>’.
|
</p>
|
<a name="Example-56"></a>
|
<h4 class="subsubheading">Example</h4>
|
|
<p>For a PPC MBX board (note: line breaks are for readability only, they
|
don’t appear in the actual output):
|
</p>
|
<div class="smallexample">
|
<pre class="smallexample">(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)
|
</pre></div>
|
|
|
<a name="The-_002ddata_002dread_002dmemory-Command"></a>
|
<h4 class="subheading">The <code>-data-read-memory</code> Command</h4>
|
<a name="index-_002ddata_002dread_002dmemory"></a>
|
|
<p>This command is deprecated, use <code>-data-read-memory-bytes</code> instead.
|
</p>
|
<a name="Synopsis-69"></a>
|
<h4 class="subsubheading">Synopsis</h4>
|
|
<div class="smallexample">
|
<pre class="smallexample"> -data-read-memory [ -o <var>byte-offset</var> ]
|
<var>address</var> <var>word-format</var> <var>word-size</var>
|
<var>nr-rows</var> <var>nr-cols</var> [ <var>aschar</var> ]
|
</pre></div>
|
|
<p>where:
|
</p>
|
<dl compact="compact">
|
<dt>‘<samp><var>address</var></samp>’</dt>
|
<dd><p>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.
|
</p>
|
</dd>
|
<dt>‘<samp><var>word-format</var></samp>’</dt>
|
<dd><p>The format to be used to print the memory words. The notation is the
|
same as for <small>GDB</small>’s <code>print</code> command (see <a href="Output-Formats.html#Output-Formats">Output Formats</a>).
|
</p>
|
</dd>
|
<dt>‘<samp><var>word-size</var></samp>’</dt>
|
<dd><p>The size of each memory word in bytes.
|
</p>
|
</dd>
|
<dt>‘<samp><var>nr-rows</var></samp>’</dt>
|
<dd><p>The number of rows in the output table.
|
</p>
|
</dd>
|
<dt>‘<samp><var>nr-cols</var></samp>’</dt>
|
<dd><p>The number of columns in the output table.
|
</p>
|
</dd>
|
<dt>‘<samp><var>aschar</var></samp>’</dt>
|
<dd><p>If present, indicates that each row should include an <small>ASCII</small> dump. The
|
value of <var>aschar</var> is used as a padding character when a byte is not a
|
member of the printable <small>ASCII</small> character set (printable <small>ASCII</small>
|
characters are those whose code is between 32 and 126, inclusively).
|
</p>
|
</dd>
|
<dt>‘<samp><var>byte-offset</var></samp>’</dt>
|
<dd><p>An offset to add to the <var>address</var> before fetching memory.
|
</p></dd>
|
</dl>
|
|
<p>This command displays memory contents as a table of <var>nr-rows</var> by
|
<var>nr-cols</var> words, each word being <var>word-size</var> bytes. In total,
|
<code><var>nr-rows</var> * <var>nr-cols</var> * <var>word-size</var></code> bytes are read
|
(returned as ‘<samp>total-bytes</samp>’). Should less than the requested number
|
of bytes be returned by the target, the missing words are identified
|
using ‘<samp>N/A</samp>’. The number of bytes read from the target is returned
|
in ‘<samp>nr-bytes</samp>’ and the starting address used to read memory in
|
‘<samp>addr</samp>’.
|
</p>
|
<p>The address of the next/previous row or page is available in
|
‘<samp>next-row</samp>’ and ‘<samp>prev-row</samp>’, ‘<samp>next-page</samp>’ and
|
‘<samp>prev-page</samp>’.
|
</p>
|
<a name="GDB-Command-51"></a>
|
<h4 class="subsubheading"><small>GDB</small> Command</h4>
|
|
<p>The corresponding <small>GDB</small> command is ‘<samp>x</samp>’. <code>gdbtk</code> has
|
‘<samp>gdb_get_mem</samp>’ memory read command.
|
</p>
|
<a name="Example-57"></a>
|
<h4 class="subsubheading">Example</h4>
|
|
<p>Read six bytes of memory starting at <code>bytes+6</code> but then offset by
|
<code>-6</code> bytes. Format as three rows of two columns. One byte per
|
word. Display each word in hex.
|
</p>
|
<div class="smallexample">
|
<pre class="smallexample">(gdb)
|
9-data-read-memory -o -6 -- bytes+6 x 1 3 2
|
9^done,addr="0x00001390",nr-bytes="6",total-bytes="6",
|
next-row="0x00001396",prev-row="0x0000138e",next-page="0x00001396",
|
prev-page="0x0000138a",memory=[
|
{addr="0x00001390",data=["0x00","0x01"]},
|
{addr="0x00001392",data=["0x02","0x03"]},
|
{addr="0x00001394",data=["0x04","0x05"]}]
|
(gdb)
|
</pre></div>
|
|
<p>Read two bytes of memory starting at address <code>shorts + 64</code> and
|
display as a single word formatted in decimal.
|
</p>
|
<div class="smallexample">
|
<pre class="smallexample">(gdb)
|
5-data-read-memory shorts+64 d 2 1 1
|
5^done,addr="0x00001510",nr-bytes="2",total-bytes="2",
|
next-row="0x00001512",prev-row="0x0000150e",
|
next-page="0x00001512",prev-page="0x0000150e",memory=[
|
{addr="0x00001510",data=["128"]}]
|
(gdb)
|
</pre></div>
|
|
<p>Read thirty two bytes of memory starting at <code>bytes+16</code> and format
|
as eight rows of four columns. Include a string encoding with ‘<samp>x</samp>’
|
used as the non-printable character.
|
</p>
|
<div class="smallexample">
|
<pre class="smallexample">(gdb)
|
4-data-read-memory bytes+16 x 1 8 4 x
|
4^done,addr="0x000013a0",nr-bytes="32",total-bytes="32",
|
next-row="0x000013c0",prev-row="0x0000139c",
|
next-page="0x000013c0",prev-page="0x00001380",memory=[
|
{addr="0x000013a0",data=["0x10","0x11","0x12","0x13"],ascii="xxxx"},
|
{addr="0x000013a4",data=["0x14","0x15","0x16","0x17"],ascii="xxxx"},
|
{addr="0x000013a8",data=["0x18","0x19","0x1a","0x1b"],ascii="xxxx"},
|
{addr="0x000013ac",data=["0x1c","0x1d","0x1e","0x1f"],ascii="xxxx"},
|
{addr="0x000013b0",data=["0x20","0x21","0x22","0x23"],ascii=" !\"#"},
|
{addr="0x000013b4",data=["0x24","0x25","0x26","0x27"],ascii="$%&'"},
|
{addr="0x000013b8",data=["0x28","0x29","0x2a","0x2b"],ascii="()*+"},
|
{addr="0x000013bc",data=["0x2c","0x2d","0x2e","0x2f"],ascii=",-./"}]
|
(gdb)
|
</pre></div>
|
|
<a name="The-_002ddata_002dread_002dmemory_002dbytes-Command"></a>
|
<h4 class="subheading">The <code>-data-read-memory-bytes</code> Command</h4>
|
<a name="index-_002ddata_002dread_002dmemory_002dbytes"></a>
|
|
<a name="Synopsis-70"></a>
|
<h4 class="subsubheading">Synopsis</h4>
|
|
<div class="smallexample">
|
<pre class="smallexample"> -data-read-memory-bytes [ -o <var>offset</var> ]
|
<var>address</var> <var>count</var>
|
</pre></div>
|
|
<p>where:
|
</p>
|
<dl compact="compact">
|
<dt>‘<samp><var>address</var></samp>’</dt>
|
<dd><p>An expression specifying the address of the first addressable memory unit
|
to be read. Complex expressions containing embedded white space should be
|
quoted using the C convention.
|
</p>
|
</dd>
|
<dt>‘<samp><var>count</var></samp>’</dt>
|
<dd><p>The number of addressable memory units to read. This should be an integer
|
literal.
|
</p>
|
</dd>
|
<dt>‘<samp><var>offset</var></samp>’</dt>
|
<dd><p>The offset relative to <var>address</var> at which to start reading. This
|
should be an integer literal. This option is provided so that a frontend
|
is not required to first evaluate address and then perform address
|
arithmetics itself.
|
</p>
|
</dd>
|
</dl>
|
|
<p>This command attempts to read all accessible memory regions in the
|
specified range. First, all regions marked as unreadable in the memory
|
map (if one is defined) will be skipped. See <a href="Memory-Region-Attributes.html#Memory-Region-Attributes">Memory Region Attributes</a>. Second, <small>GDB</small> will attempt to read the remaining
|
regions. For each one, if reading full region results in an errors,
|
<small>GDB</small> will try to read a subset of the region.
|
</p>
|
<p>In general, every single memory unit in the region may be readable or not,
|
and the only way to read every readable unit is to try a read at
|
every address, which is not practical. Therefore, <small>GDB</small> will
|
attempt to read all accessible memory units at either beginning or the end
|
of the region, using a binary division scheme. This heuristic works
|
well for reading across a memory map boundary. Note that if a region
|
has a readable range that is neither at the beginning or the end,
|
<small>GDB</small> will not read it.
|
</p>
|
<p>The result record (see <a href="GDB_002fMI-Result-Records.html#GDB_002fMI-Result-Records">GDB/MI Result Records</a>) that is output of
|
the command includes a field named ‘<samp>memory</samp>’ whose content is a
|
list of tuples. Each tuple represent a successfully read memory block
|
and has the following fields:
|
</p>
|
<dl compact="compact">
|
<dt><code>begin</code></dt>
|
<dd><p>The start address of the memory block, as hexadecimal literal.
|
</p>
|
</dd>
|
<dt><code>end</code></dt>
|
<dd><p>The end address of the memory block, as hexadecimal literal.
|
</p>
|
</dd>
|
<dt><code>offset</code></dt>
|
<dd><p>The offset of the memory block, as hexadecimal literal, relative to
|
the start address passed to <code>-data-read-memory-bytes</code>.
|
</p>
|
</dd>
|
<dt><code>contents</code></dt>
|
<dd><p>The contents of the memory block, in hex.
|
</p>
|
</dd>
|
</dl>
|
|
|
|
<a name="GDB-Command-52"></a>
|
<h4 class="subsubheading"><small>GDB</small> Command</h4>
|
|
<p>The corresponding <small>GDB</small> command is ‘<samp>x</samp>’.
|
</p>
|
<a name="Example-58"></a>
|
<h4 class="subsubheading">Example</h4>
|
|
<div class="smallexample">
|
<pre class="smallexample">(gdb)
|
-data-read-memory-bytes &a 10
|
^done,memory=[{begin="0xbffff154",offset="0x00000000",
|
end="0xbffff15e",
|
contents="01000000020000000300"}]
|
(gdb)
|
</pre></div>
|
|
|
<a name="The-_002ddata_002dwrite_002dmemory_002dbytes-Command"></a>
|
<h4 class="subheading">The <code>-data-write-memory-bytes</code> Command</h4>
|
<a name="index-_002ddata_002dwrite_002dmemory_002dbytes"></a>
|
|
<a name="Synopsis-71"></a>
|
<h4 class="subsubheading">Synopsis</h4>
|
|
<div class="smallexample">
|
<pre class="smallexample"> -data-write-memory-bytes <var>address</var> <var>contents</var>
|
-data-write-memory-bytes <var>address</var> <var>contents</var> <span class="roman">[</span><var>count</var><span class="roman">]</span>
|
</pre></div>
|
|
<p>where:
|
</p>
|
<dl compact="compact">
|
<dt>‘<samp><var>address</var></samp>’</dt>
|
<dd><p>An expression specifying the address of the first addressable memory unit
|
to be written. Complex expressions containing embedded white space should
|
be quoted using the C convention.
|
</p>
|
</dd>
|
<dt>‘<samp><var>contents</var></samp>’</dt>
|
<dd><p>The hex-encoded data to write. It is an error if <var>contents</var> does
|
not represent an integral number of addressable memory units.
|
</p>
|
</dd>
|
<dt>‘<samp><var>count</var></samp>’</dt>
|
<dd><p>Optional argument indicating the number of addressable memory units to be
|
written. If <var>count</var> is greater than <var>contents</var>’ length,
|
<small>GDB</small> will repeatedly write <var>contents</var> until it fills
|
<var>count</var> memory units.
|
</p>
|
</dd>
|
</dl>
|
|
<a name="GDB-Command-53"></a>
|
<h4 class="subsubheading"><small>GDB</small> Command</h4>
|
|
<p>There’s no corresponding <small>GDB</small> command.
|
</p>
|
<a name="Example-59"></a>
|
<h4 class="subsubheading">Example</h4>
|
|
<div class="smallexample">
|
<pre class="smallexample">(gdb)
|
-data-write-memory-bytes &a "aabbccdd"
|
^done
|
(gdb)
|
</pre></div>
|
|
<div class="smallexample">
|
<pre class="smallexample">(gdb)
|
-data-write-memory-bytes &a "aabbccdd" 16e
|
^done
|
(gdb)
|
</pre></div>
|
|
<hr>
|
<div class="header">
|
<p>
|
Next: <a href="GDB_002fMI-Tracepoint-Commands.html#GDB_002fMI-Tracepoint-Commands" accesskey="n" rel="next">GDB/MI Tracepoint Commands</a>, Previous: <a href="GDB_002fMI-Variable-Objects.html#GDB_002fMI-Variable-Objects" accesskey="p" rel="previous">GDB/MI Variable Objects</a>, Up: <a href="GDB_002fMI.html#GDB_002fMI" accesskey="u" rel="up">GDB/MI</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
|
</div>
|
|
|
|
</body>
|
</html>
|
