📄 idb_release_notes.html
字号:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Intel(R) Debugger for Linux* Release Notes</title>
<!--Release Notes Template v1.2-->
<script language="javascript">
<!--
if (navigator.userAgent.indexOf('Linux') != -1)
{
document.write("<style type='text/css'>");
document.write("body, p, h1, h2, h3, h4, th, tr, ol, ul, li{font-family: helvetica, sans-serif;}");
<!-- document.write("p, h4, li, table{margin-left: 30pt;}"); -->
<!-- document.write("h3{margin-left: 15pt;}"); -->
document.write("tr{vertical-align: top;}");
document.write("th{background-color: #eeeeee; text-align: left; padding: 4pt;}");
document.write("code{font-family: Courier, monospace}");
document.write("blockquote{background-color: #dddddd}");
document.write("</style>");
}
if (navigator.userAgent.indexOf('Win') != -1)
{
document.write("<style type='text/css'>");
document.write("body, th, tr, li{font-family: 'Times New Roman', serif;}");
document.write("p, h4, li, table{margin-left: 30pt;}");
document.write("h3{margin-left: 15pt;}");
document.write("tr{vertical-align: top;}");
document.write("th{background-color: #eeeeee; text-align: left; padding: 4pt;}");
document.write("code{font-family: Courier, monospace;}");
document.write("blockquote{margin-left: 30pt; background-color: #dddddd}");
document.write("</style>");
}
//-->
</script>
</head>
<body link="#0000ee" alink="#0000ee" vlink="#551a8b">
<h1 align="center">
Intel® Debugger for Linux* Release Notes</h1>
<h2>Contents</h2>
<p>
<a href="#Overview">Overview</a><br>
<a href="#ProductContents">Product Contents</a><br>
<a href="#SpecialFeatures">Special Features</a><br>
<a href="#NewFeatures">New Features</a><a href="#SystemReq"></a><br>
<a href="#Install">Installation Notes</a><br>
<a href="#Limitations">Known Limitations</a><br>
<a href="#Documentation">Documentation</a><br>
<a href="#TechSupport">Technical Support</a><br>
<a href="#AdditionalInfo">Additional Information</a><br>
<a href="#Legal">Copyright and Legal Information</a> </p>
<h2><a name="Overview"></a>Overview</h2>
<div style="margin-left: 40px;">
Intel® Debugger (idb) for Linux*, for versions:<br>
<div style="margin-left: 40px;">
9.1-29<br>
10.0-29 <br>
</div>
<p>
To receive technical support and updates, you need to register your Intel
Software Product. See the <a href="#TechSupport">Technical Support</a>
section.
</p>
</div>
<h2><a name="ProductContents"></a>Product Contents</h2>
<div style="margin-left: 40px;">
A fully symbolic debugger for the Linux platform. Key features allow you to:
<ul type="disc" style="background-color: rgb(255, 255, 255);">
<li style="">Perform source-level debugging </li>
<li style="">Attach to a running process</li>
<li style="">Debug programs with shared libraries</li>
<li style="">Work in a DBX- or GDB-like user interface<br>
</li>
</ul>
</p>
<p>The debugger supports the debugging of programs written in C,
C++, Fortran,
and Fortran 90. The debugger allows
evaluation of expressions using the syntax of the source programming
language. </p>
<p>
For full information about the debugger, please refer to the
following manual:
</p>
<p style="margin-left: 1in">
<big>Intel® Debugger Manual</big>
</p>
<p>
which is found in the installation directory where these release
notes reside.
</p>
</div>
<h2><a name="SpecialFeatures"></a>Special Features</h2>
<div style="margin-left: 40px">
<a href="#_Optional_Gdb-like_user_interface">Optional DBX- or GDB-like user interface</a><br>
<a href="#_GUI">Graphical User Interface (GUI)</a><br>
<a href="#_Debugging_massively_parallel"> Debugging massively parallel processing (MPP) applications</a><br>
<a href="#_Emacs_GDB_mode">Starting the debugger under Emacs</a><br>
<a href="#_Debugging_OpenMP_applications">Debugging OpenMP applications</a>
</p>
<h3><a name="_Optional_Gdb-like_user_interface"></a>
Optional DBX- or GDB-like user interface</h3>
<p>
Users can switch to the DBX- or GDB-like interface, depending on their
preference. In Compiler version 9.1 and older, the default interface
is DBX. In Compiler version 10.0 Beta and newer, the default interface
is GDB (when running "idb" from the installed location), except in the GUI
(where the default is DBX).
The DBX and GDB command set (and
debugger output) are supported as described in the manual.
<br><br>
To activate GDB mode, use the <i>-gdb</i>
command line option (if it is not the default), or set the debugger
variable <i>$cmdset</i> to <i>gdb</i> after starting the debugger,
e.g.:
</p>
<p><code>
(idb) set $cmdset="gdb"
</code> </p>
<p>
To activate DBX mode, use the <i>-dbx</i>
command line option (if it is not the default), or set the debugger
variable <i>$cmdset</i> to <i>dbx</i> after starting the debugger,
e.g.:
</p>
<p><code>
(idb) set $cmdset="dbx"
</code> </p>
<h3><a name="_GUI"></a>Graphical User Interface (GUI)<br>
</h3>
<p>
A GUI is now available. Just use the <b>-gui</b> flag when
invoking the debugger from the Linux command line.<br><br>
Only the DBX-like interface is available from within the GUI.
</p>
<h3><a name="_Debugging_massively_parallel"></a>
Debugging massively parallel processing (MPP) applications</h3>
<p>
Debugging MPI applications compiled with <code>mpich</code>
or Intel MPI 3.0 is supported to the extent described in the manual
(Section <i>Debugging Parallel Applications</i>).<br>
</p>
<h3><a name="_Emacs_GDB_mode"></a>
Starting the debugger under Emacs</h3>
<p>
The manual describes how to start the debugger in default mode
under Emacs. To start the debugger in GDB mode under Emacs, do the
following. </p>
<ol>
<li>Select "Debugger..." under the Emacs "Tools" menu. </li>
<li>At the "Run gdb (like this): " prompt, type <code><b>idb -gdb -fullname</b></code> </li>
</ol>
<p>
To use the GDB-like interface, do not load the <code>idb.el</code> file
documented in the manual.
</p>
<h3><a name="_Debugging_OpenMP_applications"></a>
Debugging OpenMP applications</h3>
<p>
When debugging an OpenMP application, the debugger is capable of
providing useful information on OpenMP locks, teams, and threads.
</p>
</div>
<h2><a name="NewFeatures"></a>New Features</h2>
<div style="margin-left: 40px">
All compiler versions:
<br>
<div style="margin-left: 40px">
All platforms:
<div style="margin-left: 40px;">
<a href="#ENHANCED_MPI_SUPPORT_">
Enhanced MPI Support</a><br>
<a href="#ENHANCED_GDB_">
Enhanced GDB compatibility</a><br>
<a href="#PENDING_BPT_">
Support for Pending Breakpoints</a><br>
</div>
<br>
IA-32 & Itanium®:
<div style="margin-left: 40px;">
<a href="#EclipseStartup_">Eclipse* Support </a><br>
</div>
</div>
</div>
</div>
<br>
<div style="margin-left: 40px">
Compiler Version 9.1:
<br>
<div style="margin-left: 40px;">
All platforms:
<div style="margin-left: 40px;">
<a href="#OpenMP_Support_">OpenMP Support</a><br>
</div>
</div>
</div>
</div>
<br>
<div style="margin-left: 40px">
Compiler Version 10.0:
<br>
<div style="margin-left: 40px;">
Intel® 64 & Itanium®:
<div style="margin-left: 40px;">
<a href="#CLOMP_">Intel® Cluster OpenMP Support</a><br>
</div>
</div>
</div>
<div style="margin-left: 40px">
<h3> <a name="ENHANCED_MPI_SUPPORT_">
Enhanced MPI Support</a></h3>
<p>
The debugger is now capable of debugging a fresh MPI job that
uses the MPICH or the Intel MPI 3.0 libraries. In addition, it is
capable of attaching to an existing MPI job that uses MPICH.
</p>
<p>
Before you start debugging a MPI job with the debugger,
make sure you have the environment variable <code>IDB_HOME</code>
set to the directory where the debugger is installed.
</p>
<p>
To start a fresh MPI job under the debugger's control, do
the following:
<ul>
<li>If you use MPICH
<code><pre><strong>% mpirun -dbg=idb -np <<i>number of processes</i>> [<i>other MPICH options</i> ] <<i>executable</i>> [<i>arguments to the executable</i>]</strong>
</code></pre>
Note that you need to copy the script <code>mpirun_dbg.idb</code>
that comes with the debugger's package to the <code>bin</code>
directory of you MPICH installation.
</li><br><br>
<li>If you use Intel MPI 3.0
<code><pre><strong>% mpiexec -idb -n <<i>number of processes</i>> [<i>other Intel MPI options</i> ] <<i>executable</i>> [<i>arguments to the executable</i>]</strong>
</pre></code></li>
</ul>
</p>
<p>To attach to an existing MPICH job, do this:
<p><code><pre>
<strong>% idb -pid <<i>launcher pid</i>> -parallelattach <<i>executable</i> ></strong>
</code></pre></p>
<p>
The <i><launcher pid></i> is the ID of the launcher process that
spawned all the processes in the job. You can use the Linux
command "<b><code>ps -xf</code></b>" to find the ID of this process.
The <i><executable></i> is the name of the launcher executable.
</p>
</p>
<p>See <a href="#MPP_Debugging_Restrictions">Known Limitations</a> for a list of issues with MPI support.
</p>
<p>See Chapter 19 of the manual for further information on
this support.
</p>
<h3> <a name=ENHANCED_GDB_>
Enhanced GDB compatibility</a></h3>
<p>
These release features more GDB compatibility features. Included are the
following features:
<ul>
<li><a href="#DDD_"> Better DDD compatibility</a>
<li><a href="#INITFILES_"> Support for initialization files</a>
<li><a href="#HISTFILES_GDB_"> Support for command history</a>
<li><a href="#CMDLINE_OPTS_"> More GDB command line options</a>
<li><a href="#INFO_"> Support for <code>info variables</code>,
<code>info types</code> and
<code>info functions</code></a>
<li><a href="#COMPLETE_"> Command, filename and variable completion</a>
<li><a href="#UDC_"> Support for user-defined commands</a>
</ul>
<h4><a name="DDD_"> Better DDD Compatibility</a></h4>
<p>
Several bugs have been fixed in IDB's support for DDD.
To use DDD, users should use this command:<br>
<code><b>ddd --debugger "idb -gdb"</b></code>
</p>
<h4><a name=INITFILES_> Initialization files</a></h4>
<p>
Initialization files are supported in both DBX mode and GDB mode.
</p>
<p><b>DBX mode behavior</b><br>
Before attaching to or starting a target executable and before
processing command line qualifiers, the debugger reads <i>.idbrc</i> in
the current directory and executes it. If there is no <i>.idbrc</i> in
the current directory, the debugger tries to read it from the
user's home directory. If the <i>-i</i> option is passed, defining
another initialization file, then it will be used instead of <i>.idbrc</i>.
<p>
After the target process has been loaded or attached to, and
after processing command line qualifiers, the debugger reads
<i>.dbxinit</i>
in the current directory and executes it. If there is no <i>.dbxinit</i>
in
the current directory, the debugger tries to read it from the user's
home directory. If the option <i>-c</i> is passed, defining another
initialization file, then it will be used instead of <i>.dbxinit</i>.
<p>
<b>GDB mode behavior</b><br>
Before attaching to
or starting a target executable the debugger reads <i>.gdbinit</i> in the
user's home directory. After attaching to, or loading the target
executable, the debugger reads <i>.gdbinit</i> in the current
working directory. If the user's current working directory is the same as
the user's home directory, then <i>.gdbinit</i> is read
before attaching to or starting the target exeutable.
<p>
The debugger will read any command files specified by the <i>-x</i> option
in addition to <i>.gdbinit</i>. Additionally, it will read the
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -