Intel® Debugger Command Reference May 2009 Document Number: 319698-009US World Wide Web: http://www.intel.com Disclaimer and Legal Information INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL’S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. UNLESS OTHERWISE AGREED IN WRITING BY INTEL, THE INTEL PRODUCTS ARE NOT DESIGNED NOR INTENDED FOR ANY APPLICATION IN WHICH THE FAILURE OF THE INTEL PRODUCT COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR. Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked reserved or undefined. Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information. The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or by visiting Intel’s Web Site. Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across different processor families. See http://www.intel.com/products/processor_number for details. BunnyPeople, Celeron, Celeron Inside, Centrino, Centrino Atom, Centrino Atom Inside, Centrino Inside, Centrino logo, Core Inside, FlashFile, i960, InstantIP, Intel, Intel logo, Intel386, Intel486, IntelDX2, IntelDX4, IntelSX2, Intel Atom, Intel Atom Inside, Intel Core, Intel Inside, Intel Inside logo, Intel. Leap ahead., Intel. Leap ahead. logo, Intel NetBurst, Intel NetMerge, Intel NetStructure, Intel SingleDriver, Intel SpeedStep, Intel StrataFlash, Intel Viiv, Intel vPro, Intel XScale, Itanium, Itanium Inside, MCS, MMX, Oplus, OverDrive, PDCharm, Pentium, Pentium Inside, skoool, Sound Mark, The Journey Inside, Viiv Inside, vPro Inside, VTune, Xeon, and Xeon Inside are trademarks of Intel Corporation in the U.S. and other countries. * Other names and brands may be claimed as the property of others. 2 Copyright © 2001-2009, Intel Corporation. All rights reserved. Portions Copyright © 2001, Hewlett-Packard Development Company, L.P. 3 Welcome to the Intel® Debugger 1 Introducing the Intel® Debugger The Intel® Debugger (IDB) is a full-featured symbolic source code application debugger that helps programmers: •debug programs • disassemble and examine machine code and examine machine register values • debug programs with shared libraries • debug multithreaded applications A GUI and command-line interface are available on systems based on IA-32 or Intel® 64 architecture running Linux* OS. A command-line interface is available on the following systems: • Systems based on the IA-32 architecture running Mac OS* X • Systems based on the Intel® 64 architecture running Mac OS X • Systems based on IA-64 architecture running Linux OS The debugger features include: • C/C++ language support • Fortran language support including Fortran 95/90 • Assembler language support • Access to the registers your application accesses • Bitfield editor to modify registers • MMU support 5 1 Intel® Debugger Command Reference The Intel® Debugger facilitates developing parallelism into applications based on the parallel C++ language extensions of the Intel® C++ compiler or the Intel® OpenMP* runtime environment. The Intel® Debugger offers the following parallel debugging features: • Thread data sharing analysis, to detect accesses to identical data elements from different threads. NOTE. Thread data sharing detection is limited to applications that use the parallel language extensions of the Intel® C++ Compiler. To analyze threading errors in other applications, it is recommended to use the Intel® Thread Checker. The Intel® Thread Checker includes a patented advanced error detection engine for finding data races and deadlocks. • A smart breakpoint to stop program execution on re-entrant function calls from different threads. • A mode for simulating serial execution of OpenMP* code, which is useful for debugging OpenMP code. You can enable or disable the creation of additional worker threads in OpenMP parallel loops dynamically. • A set of OpenMP runtime information views for advanced OpenMP program state analysis. • An SSE (Streaming SIMD Extensions) register view with extensive formatting and editing options for debugging parallel data using the SIMD (Single Instruction, Multiple Data) instruction set. NOTE. The Intel Debugger is designed for and tested on Intel processors. Incompatible or proprietary instructions supported by non-Intel processors might cause the analysis capabilities of this product to function incorrectly. Attempts to analyze code not supported by Intel processors could result in failures in this product. See Also Related Information Notational Conventions Related Information The Release Notes contain product features or changes in the product that may not be documented elsewhere. Release Notes are included in the product installation. 6 Notational Conventions Convention Explanation Example Italic Italic is used for emphasis, Do not close the project without saving. the introduction of new terms, The filename consists of the basename and the denotation of terms, extension. placeholders, The expression and/or denotes an inclusive titles of manuals. choice between two or more items. The bitmap is width pixels wide and len pixels high. For more information, refer to the Intel® Linker Manual. Bold Text in boldface denotes The Cancel button of the Start dialog box elements of the graphical user interface. Monospace Monospace indicates ippsapi.h filenames, \alt\include directory names and ecl -O2 pathnames, commands and command-line Use the CreateObj() function to … options, function names, methods, printf("hello, world\n"); classes, data structures in body text, source code. Monospace Italic monospace indicates ippiMalloc( int width, int* pStep); italic source code parameters, arguments, or other placeholders. -7 Intel® Debugger Command Reference Convention Explanation Example Monospace Bold monospace indicates [c:] dir bold what you type as input on a command line or emphasizes parts of source x = ( h > 0 ? sizeof(m) : 0xF ) + min; code. [ ] Items enclosed in brackets are Fa[c] optional. Indicates Fa or Fac. { | } Braces and vertical bars X{A | B | C} indicate the choice of one item Indicates one of XA, XB, and XC. from a selection of two or more items. "[" "]" "{" Writing a metacharacter in "[" X "]" [ Y ] "}" "|" quotation marks negates the denotes the letter X enclosed in brackets, syntactical meaning stated optionally followed by the letter Y. above; the character is taken as a literal. … The ellipsis indicates that the filename … previous item can be repeated Indicates that one or more filenames can be several times. specified. ,… The ellipsis preceded by a word ,… comma indicates that the Indicates that one or more words can be previous item can be repeated specified. If more than one word is specified, several times, separated by the words are comma-separated. commas. > Indicates a menu item inside File > Close a menu. indicates to select the Close item from the File menu. -8 Before You Begin 2 Preparing the Debugging Environment When you start the debugger, it captures the environment of the shell that launches the debugger. When you debug an MPI application, the debugger uses the environment of the leaf debugger's shell, capturing this environment when you launch the debugger. The shell’s environment variables include PATH, LD_LIBRARY_PATH, SHELL and HOME. To modify the captured enviroment, use the set environment command. To display the captured environment, use the show environment command. Changes you make to the captured environment only affect debuggees that are started after you make the change. They have no effect on the debugger itself until you restart the debugger. To see the list of environment variables, use the printenv shell command before starting the debugger. See Also set environment (gdb mode only) show environment (gdb mode only) Configuring the Debugger Configuring Default Startup Actions Using Initialization Files You can use an initialization file to execute specific commands when the debugger starts up. For example, you can create an initialization file to load a debuggee as soon as the debugger starts. 9 2 Intel® Debugger Command Reference You can have an initialization file in your home directory as well as in your project directory. You can connect to the target in the initialization file in your home directory, and use the project initialization