| <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> |
| <html> |
| <!-- Copyright (C) 1988-2015 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.2, http://www.gnu.org/software/texinfo/ --> |
| <head> |
| <title>Debugging with GDB: Target Commands</title> |
| |
| <meta name="description" content="Debugging with GDB: Target Commands"> |
| <meta name="keywords" content="Debugging with GDB: Target Commands"> |
| <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="Targets.html#Targets" rel="up" title="Targets"> |
| <link href="Byte-Order.html#Byte-Order" rel="next" title="Byte Order"> |
| <link href="Active-Targets.html#Active-Targets" rel="prev" title="Active Targets"> |
| <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="Target-Commands"></a> |
| <div class="header"> |
| <p> |
| Next: <a href="Byte-Order.html#Byte-Order" accesskey="n" rel="next">Byte Order</a>, Previous: <a href="Active-Targets.html#Active-Targets" accesskey="p" rel="prev">Active Targets</a>, Up: <a href="Targets.html#Targets" accesskey="u" rel="up">Targets</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="Commands-for-Managing-Targets"></a> |
| <h3 class="section">19.2 Commands for Managing Targets</h3> |
| |
| <dl compact="compact"> |
| <dt><code>target <var>type</var> <var>parameters</var></code></dt> |
| <dd><p>Connects the <small>GDB</small> host environment to a target machine or |
| process. A target is typically a protocol for talking to debugging |
| facilities. You use the argument <var>type</var> to specify the type or |
| protocol of the target machine. |
| </p> |
| <p>Further <var>parameters</var> are interpreted by the target protocol, but |
| typically include things like device names or host names to connect |
| with, process numbers, and baud rates. |
| </p> |
| <p>The <code>target</code> command does not repeat if you press <tt class="key">RET</tt> again |
| after executing the command. |
| </p> |
| <a name="index-help-target"></a> |
| </dd> |
| <dt><code>help target</code></dt> |
| <dd><p>Displays the names of all targets available. To display targets |
| currently selected, use either <code>info target</code> or <code>info files</code> |
| (see <a href="Files.html#Files">Commands to Specify Files</a>). |
| </p> |
| </dd> |
| <dt><code>help target <var>name</var></code></dt> |
| <dd><p>Describe a particular target, including any parameters necessary to |
| select it. |
| </p> |
| <a name="index-set-gnutarget"></a> |
| </dd> |
| <dt><code>set gnutarget <var>args</var></code></dt> |
| <dd><p><small>GDB</small> uses its own library BFD to read your files. <small>GDB</small> |
| knows whether it is reading an <em>executable</em>, |
| a <em>core</em>, or a <em>.o</em> file; however, you can specify the file format |
| with the <code>set gnutarget</code> command. Unlike most <code>target</code> commands, |
| with <code>gnutarget</code> the <code>target</code> refers to a program, not a machine. |
| </p> |
| <blockquote> |
| <p><em>Warning:</em> To specify a file format with <code>set gnutarget</code>, |
| you must know the actual BFD name. |
| </p></blockquote> |
| |
| <p>See <a href="Files.html#Files">Commands to Specify Files</a>. |
| </p> |
| <a name="index-show-gnutarget"></a> |
| </dd> |
| <dt><code>show gnutarget</code></dt> |
| <dd><p>Use the <code>show gnutarget</code> command to display what file format |
| <code>gnutarget</code> is set to read. If you have not set <code>gnutarget</code>, |
| <small>GDB</small> will determine the file format for each file automatically, |
| and <code>show gnutarget</code> displays ‘<samp>The current BFD target is "auto"</samp>’. |
| </p></dd> |
| </dl> |
| |
| <a name="index-common-targets"></a> |
| <p>Here are some common targets (available, or not, depending on the GDB |
| configuration): |
| </p> |
| <dl compact="compact"> |
| <dd><a name="index-target"></a> |
| </dd> |
| <dt><code>target exec <var>program</var></code></dt> |
| <dd><a name="index-executable-file-target"></a> |
| <p>An executable file. ‘<samp>target exec <var>program</var></samp>’ is the same as |
| ‘<samp>exec-file <var>program</var></samp>’. |
| </p> |
| </dd> |
| <dt><code>target core <var>filename</var></code></dt> |
| <dd><a name="index-core-dump-file-target"></a> |
| <p>A core dump file. ‘<samp>target core <var>filename</var></samp>’ is the same as |
| ‘<samp>core-file <var>filename</var></samp>’. |
| </p> |
| </dd> |
| <dt><code>target remote <var>medium</var></code></dt> |
| <dd><a name="index-remote-target"></a> |
| <p>A remote system connected to <small>GDB</small> via a serial line or network |
| connection. This command tells <small>GDB</small> to use its own remote |
| protocol over <var>medium</var> for debugging. See <a href="Remote-Debugging.html#Remote-Debugging">Remote Debugging</a>. |
| </p> |
| <p>For example, if you have a board connected to <samp>/dev/ttya</samp> on the |
| machine running <small>GDB</small>, you could say: |
| </p> |
| <div class="smallexample"> |
| <pre class="smallexample">target remote /dev/ttya |
| </pre></div> |
| |
| <p><code>target remote</code> supports the <code>load</code> command. This is only |
| useful if you have some other way of getting the stub to the target |
| system, and you can put it somewhere in memory where it won’t get |
| clobbered by the download. |
| </p> |
| </dd> |
| <dt><code>target sim <span class="roman">[</span><var>simargs</var><span class="roman">]</span> …</code></dt> |
| <dd><a name="index-built_002din-simulator-target"></a> |
| <p>Builtin CPU simulator. <small>GDB</small> includes simulators for most architectures. |
| In general, |
| </p><div class="smallexample"> |
| <pre class="smallexample"> target sim |
| load |
| run |
| </pre></div> |
| <p>works; however, you cannot assume that a specific memory map, device |
| drivers, or even basic I/O is available, although some simulators do |
| provide these. For info about any processor-specific simulator details, |
| see the appropriate section in <a href="Embedded-Processors.html#Embedded-Processors">Embedded |
| Processors</a>. |
| </p> |
| </dd> |
| <dt><code>target native</code></dt> |
| <dd><a name="index-native-target"></a> |
| <p>Setup for local/native process debugging. Useful to make the |
| <code>run</code> command spawn native processes (likewise <code>attach</code>, |
| etc.) even when <code>set auto-connect-native-target</code> is <code>off</code> |
| (see <a href="Starting.html#set-auto_002dconnect_002dnative_002dtarget">set auto-connect-native-target</a>). |
| </p> |
| </dd> |
| </dl> |
| |
| <p>Different targets are available on different configurations of <small>GDB</small>; |
| your configuration may have more or fewer targets. |
| </p> |
| <p>Many remote targets require you to download the executable’s code once |
| you’ve successfully established a connection. You may wish to control |
| various aspects of this process. |
| </p> |
| <dl compact="compact"> |
| <dt><code>set hash</code></dt> |
| <dd><a name="index-set-hash_002c-for-remote-monitors"></a> |
| <a name="index-hash-mark-while-downloading"></a> |
| <p>This command controls whether a hash mark ‘<samp>#</samp>’ is displayed while |
| downloading a file to the remote monitor. If on, a hash mark is |
| displayed after each S-record is successfully downloaded to the |
| monitor. |
| </p> |
| </dd> |
| <dt><code>show hash</code></dt> |
| <dd><a name="index-show-hash_002c-for-remote-monitors"></a> |
| <p>Show the current status of displaying the hash mark. |
| </p> |
| </dd> |
| <dt><code>set debug monitor</code></dt> |
| <dd><a name="index-set-debug-monitor"></a> |
| <a name="index-display-remote-monitor-communications"></a> |
| <p>Enable or disable display of communications messages between |
| <small>GDB</small> and the remote monitor. |
| </p> |
| </dd> |
| <dt><code>show debug monitor</code></dt> |
| <dd><a name="index-show-debug-monitor"></a> |
| <p>Show the current status of displaying communications between |
| <small>GDB</small> and the remote monitor. |
| </p></dd> |
| </dl> |
| |
| <dl compact="compact"> |
| <dd> |
| <a name="index-load-filename"></a> |
| </dd> |
| <dt><code>load <var>filename</var></code></dt> |
| <dd><a name="load"></a><p>Depending on what remote debugging facilities are configured into |
| <small>GDB</small>, the <code>load</code> command may be available. Where it exists, it |
| is meant to make <var>filename</var> (an executable) available for debugging |
| on the remote system—by downloading, or dynamic linking, for example. |
| <code>load</code> also records the <var>filename</var> symbol table in <small>GDB</small>, like |
| the <code>add-symbol-file</code> command. |
| </p> |
| <p>If your <small>GDB</small> does not have a <code>load</code> command, attempting to |
| execute it gets the error message “<code>You can't do that when your |
| target is …</code>” |
| </p> |
| <p>The file is loaded at whatever address is specified in the executable. |
| For some object file formats, you can specify the load address when you |
| link the program; for other formats, like a.out, the object file format |
| specifies a fixed address. |
| </p> |
| <p>Depending on the remote side capabilities, <small>GDB</small> may be able to |
| load programs into flash memory. |
| </p> |
| <p><code>load</code> does not repeat if you press <tt class="key">RET</tt> again after using it. |
| </p></dd> |
| </dl> |
| |
| <hr> |
| <div class="header"> |
| <p> |
| Next: <a href="Byte-Order.html#Byte-Order" accesskey="n" rel="next">Byte Order</a>, Previous: <a href="Active-Targets.html#Active-Targets" accesskey="p" rel="prev">Active Targets</a>, Up: <a href="Targets.html#Targets" accesskey="u" rel="up">Targets</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> |
