3 <title>Debugging with GDB
</title>
4 <meta http-equiv=
"Content-Type" content=
"text/html">
5 <meta name=
"description" content=
"Debugging with GDB">
6 <meta name=
"generator" content=
"makeinfo 4.3">
7 <link href=
"http://www.gnu.org/software/texinfo/" rel=
"generator-home">
12 Node:
<a name=
"Shell%20Commands">Shell Commands
</a>,
13 Previous:
<a rel=
"previous" accesskey=
"p" href=
"Quitting-GDB.html#Quitting%20GDB">Quitting GDB
</a>,
14 Up:
<a rel=
"up" accesskey=
"u" href=
"Invocation.html#Invocation">Invocation
</a>
18 <h3 class=
"section">Shell commands
</h3>
20 <p>If you need to execute occasional shell commands during your
21 debugging session, there is no need to leave or suspend GDB; you can
22 just use the
<code>shell
</code> command.
25 <dt><code>shell
</code><var>command string
</var><code></code>
26 <dd>Invoke a standard shell to execute
<var>command string
</var>.
27 If it exists, the environment variable
<code>SHELL
</code> determines which
28 shell to run. Otherwise GDB uses the default shell
29 (
<code>/bin/sh
</code> on Unix systems,
<code>COMMAND.COM
</code> on MS-DOS, etc.).
32 <p>The utility
<code>make
</code> is often needed in development environments.
33 You do not have to use the
<code>shell
</code> command for this purpose in
37 <dt><code>make
</code><var>make-args
</var><code></code>
38 <dd>Execute the
<code>make
</code> program with the specified
39 arguments. This is equivalent to
<code>shell make
</code><var>make-args
</var><code></code>.