DOCSLIB.ORG

Debugging a Program with Dbx

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Debugging a Program with Dbx Debugging a Program With dbx Sun™ Studio 11 Sun Microsystems, Inc. www.sun.com Part No 819-3683-10 November 2005, Revision A Submit comments about this document at: http://www.sun.com/hwdocs/feedback Copyright © 2005 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. Use is subject to license terms. This distribution may include materials developed by third parties. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, Java, and JavaHelp are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon architecture developed by Sun Microsystems, Inc. This product is covered and controlled by U.S. Export Control laws and may be subject to the export or import laws in other countries. Nuclear, missile, chemical biological weapons or nuclear maritime end uses or end users, whether direct or indirect, are strictly prohibited. Export or reexport to countries subject to U.S. embargo or to entities identified on U.S. export exclusion lists, including, but not limited to, the denied persons and specially designated nationals lists is strictly prohibited. DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Copyright © 2005 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, Etats-Unis. Tous droits réservés. L’utilisation est soumise aux termes de la Licence. Cette distribution peut comprendre des composants développés par des tierces parties. Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd. Sun, Sun Microsystems, le logo Sun, Java, et JavaHelp sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays.Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc. Ce produit est soumis à la législation américaine en matière de contrôle des exportations et peut être soumis à la règlementation en vigueur dans d’autres pays dans le domaine des exportations et importations. Les utilisations, ou utilisateurs finaux, pour des armes nucléaires,des missiles, des armes biologiques et chimiques ou du nucléaire maritime, directement ou indirectement, sont strictement interdites. Les exportations ou réexportations vers les pays sous embargo américain, ou vers des entités figurant sur les listes d’exclusion d’exportation américaines, y compris, mais de manière non exhaustive, la liste de personnes qui font objet d’un ordre de ne pas participer, d’une façon directe ou indirecte, aux exportations des produits ou des services qui sont régis par la législation américaine en matière de contrôle des exportations et la liste de ressortissants spécifiquement désignés, sont rigoureusement interdites. LA DOCUMENTATION EST FOURNIE "EN L’ÉTAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L’APTITUDE A UNE UTILISATION PARTICULIERE OU A L’ABSENCE DE CONTREFAÇON. Contents Before You Begin 25 How This Book Is Organized 25 Typographic Conventions 27 Shell Prompts 28 Supported Platforms 28 Accessing Sun Studio Software and Man Pages 28 Accessing Sun Studio Documentation 31 Accessing Related Solaris Documentation 35 Resources for Developers 35 Contacting Sun Technical Support 36 Sending Your Comments 36 1. Getting Started With dbx 37 Compiling Your Code for Debugging 37 Starting dbx and Loading Your Program 38 Running Your Program in dbx 40 Debugging Your Program With dbx 41 Examining a Core File 41 Setting Breakpoints 43 Stepping Through Your Program 44 3 Looking at the Call Stack 45 Examining Variables 46 Finding Memory Access Problems and Memory Leaks 47 Quitting dbx 48 Accessing dbx Online Help 48 2. Starting dbx 49 Starting a Debugging Session 49 Debugging a Core File 50 Debugging a Core File in the Same Operating Environment 51 If Your Core File Is Truncated 51 Debugging a Mismatched Core File 52 Using the Process ID 54 The dbx Startup Sequence 55 Setting Startup Properties 56 Mapping the Compile-time Directory to the Debug-time Directory 56 Setting dbx Environment Variables 57 Creating Your Own dbx Commands 57 Compiling a Program for Debugging 57 Debugging Optimized Code 58 Code Compiled Without the -g Option 58 Shared Libraries Require the -g Option for Full dbx Support 59 Completely Stripped Programs 59 Quitting Debugging 59 Stopping a Process Execution 60 Detaching a Process From dbx 60 Killing a Program Without Terminating the Session 60 Saving and Restoring a Debugging Run 61 Using the save Command 61 4 Debugging a Program With dbx • November 2005 Saving a Series of Debugging Runs as Checkpoints 63 Restoring a Saved Run 63 Saving and Restoring Using replay 64 3. Customizing dbx 65 Using the dbx Initialization File 65 Creating a .dbxrc File 66 Initialization File Sample 66 Setting dbx Environment Variables 66 The dbx Environment Variables and the Korn Shell 72 4. Viewing and Navigating To Code 73 Navigating To Code 73 Navigating To a File 74 Navigating To Functions 74 Printing a Source Listing 75 Walking the Call Stack to Navigate To Code 76 Types of Program Locations 76 Program Scope 76 Variables That Reflect the Current Scope 77 Visiting Scope 77 Qualifying Symbols With Scope Resolution Operators 79 Backquote Operator 79 C++ Double Colon Scope Resolution Operator 79 Block Local Operator 80 Linker Names 82 Locating Symbols 82 Printing a List of Occurrences of a Symbol 82 Determining Which Symbol dbx Uses 83 Contents 5 Scope Resolution Search Path 84 Relaxing the Scope Lookup Rules 84 Viewing Variables, Members, Types, and Classes 85 Looking Up Definitions of Variables, Members, and Functions 85 Looking Up Definitions of Types and Classes 87 Debugging Information in Object files and Executables 89 Object File Loading 89 Listing Debugging Information for Modules 90 Listing Modules 91 Finding Source and Object Files 91 5. Controlling Program Execution 93 Running a Program 93 Attaching dbx to a Running Process 94 Detaching dbx From a Process 95 Stepping Through a Program 96 Single Stepping 97 Continuing Execution of a Program 97 Calling a Function 98 Using Ctrl+C to Stop a Process 100 6. Setting Breakpoints and Traces 101 Setting Breakpoints 101 Setting a stop Breakpoint at a Line of Source Code 102 Setting a stop Breakpoint in a Function 103 Setting Multiple Breaks in C++ Programs 104 Setting Data Change Breakpoints 106 Setting Filters on Breakpoints 109 Tracing Execution 112 6 Debugging a Program With dbx • November 2005 Setting a Trace 112 Controlling the Speed of a Trace 112 Directing Trace Output to a File 113 Setting a when Breakpoint at a Line 113 Setting a Breakpoint in a Shared Library 113 Listing and Clearing Breakpoints 114 Listing Breakpoints and Traces 114 Deleting Specific Breakpoints Using Handler ID Numbers 114 Enabling and Disabling Breakpoints 115 Efficiency Considerations 115 7. Using the Call Stack 117 Finding Your Place on the Stack 117 Walking the Stack and Returning Home 118 Moving Up and Down the Stack 118 Moving Up the Stack 118 Moving Down the Stack 119 Moving to a Specific Frame 119 Popping the Call Stack 119 Hiding Stack Frames 120 Displaying and Reading a Stack Trace 121 8. Evaluating and Displaying Data 123 Evaluating Variables and Expressions 123 Verifying Which Variable dbx Uses 123 Variables Outside the Scope of the Current Function 124 Printing the Value of a Variable, Expression, or Identifier 124 Printing C++ 124 Dereferencing Pointers 126 Contents 7 Monitoring Expressions 126 Turning Off Display (Undisplaying) 127 Assigning a Value to a Variable 127 Evaluating Arrays 127 Array Slicing 128 Slices 131 Strides 132 9. Using Runtime Checking 135 Capabilities of Runtime Checking 136 When to Use Runtime Checking 136 Runtime Checking Requirements 136 Limitations 137 Using Runtime Checking 137 Turning On Memory Use and Memory Leak Checking 137 Turning On Memory Access Checking 138 Turning On All Runtime Checking 138 Turning Off Runtime Checking 138 Running Your Program 139 Using Access Checking 142 Understanding the Memory Access Error Report 143 Memory Access Errors 143 Using Memory Leak Checking 144 Detecting Memory Leak Errors 145 Possible Leaks 145 Checking for Leaks 146 Understanding the Memory Leak Report 147 Fixing Memory Leaks 150 Using Memory Use Checking 150 8 Debugging a Program With dbx • November 2005 Suppressing Errors 152 Types of Suppression 152 Suppressing Error Examples 153 Default Suppressions 154 Using Suppression to Manage Errors 154 Using Runtime Checking on a Child Process 155 Using Runtime Checking on an Attached Process 159 Using Fix and Continue With Runtime Checking 160 Runtime Checking Application Programming Interface 162 Using Runtime Checking in Batch Mode 162 bcheck Syntax 163 bcheck Examples 163 Enabling Batch Mode Directly From dbx 164 Troubleshooting Tips 164 Runtime Checking’s 8 Megabyte Limit 164 Runtime Checking Errors 166 Access Errors 166 Memory Leak Errors 169 10.
Load more

Recommended publications
  • Using Restricted Transactional Memory to Build a Scalable In-Memory Database
    Using Restricted Transactional Memory to Build a Scalable In-Memory Database Zhaoguo Wang†, Hao Qian‡, Jinyang Li§, Haibo Chen‡ † School of Computer Science, Fudan University ‡ Institute of Parallel and Distributed Systems, Shanghai Jiao Tong University § Department of Computer Science, New York University Abstract However, the correctness of the resulting code is complex to reason about and relies on the processor’s (increasingly The recent availability of Intel Haswell processors marks the complex) memory model. transition of hardware transactional memory from research Recently, Intel has shipped its 4th-generation Haswell toys to mainstream reality. DBX is an in-memory database processor with support for Hardware Transactional Mem- that uses Intel’s restricted transactional memory (RTM) to ory [16]. This opens up a third possibility to scaling multi- achieve high performance and good scalability across multi- core software. Instead of relying on fine-grained locking core machines. The main limitation (and also key to practi- and atomic operations, one can synchronize using hardware cality) of RTM is its constrained working set size: an RTM transactions, which offer a programming model that is ar- region that reads or writes too much data will always be guably even more straightforward than mutual exclusion. aborted. The design of DBX addresses this challenge in sev- The promise is that the resulting implementation is much eral ways. First, DBX builds a database transaction layer on simpler and easier-to-understand while still retaining the top of an underlying shared-memory store. The two layers performance benefits of fine-grained locking. use separate RTM regions to synchronize shared memory Does hardware transactional memory actually deliver its access.
    [Show full text]
  • Using the GNU Compiler Collection (GCC)
    Using the GNU Compiler Collection (GCC) Using the GNU Compiler Collection by Richard M. Stallman and the GCC Developer Community Last updated 23 May 2004 for GCC 3.4.6 For GCC Version 3.4.6 Published by: GNU Press Website: www.gnupress.org a division of the General: [email protected] Free Software Foundation Orders: [email protected] 59 Temple Place Suite 330 Tel 617-542-5942 Boston, MA 02111-1307 USA Fax 617-542-2652 Last printed October 2003 for GCC 3.3.1. Printed copies are available for $45 each. Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 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.2 or any later version published by the Free Software Foundation; with the Invariant Sections being \GNU General Public License" and \Funding Free Software", the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled \GNU Free Documentation License". (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Short Contents Introduction ...................................... 1 1 Programming Languages Supported by GCC ............ 3 2 Language Standards Supported by GCC ............... 5 3 GCC Command Options .........................
    [Show full text]
  • Oracle Solaris Studio 12.3 Debugging a Program With
    Oracle® Solaris Studio 12.3: Debugging a ProgramWith dbx Part No: E21993 December 2011 Copyright © 1992, 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms setforth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
    [Show full text]
  • A Short User Manual for Dbx
    A Short User Manual for dbx \dbx" is the name of the debugger that is available for use on many Unix systems. This document is intended to list the most common dbx commands and briefly explain how to use them. It is not a complete description of dbx but should be a sufficient reference to get started. For a more detailed description or to find out about other commands and options, execute the command % man dbx or from within dbx use the 'help' command (recommended). Subjects covered below: let (dbx) be the prompt while in dbx mode: a) Compiling your code for use with the debugger [ cc with -g flag] b) Starting the debugger [ \%dbx executable ] c) Getting help while using the debugger [ (dbx) help ] d) Running your program in the debugger [ (dbx) run ] e) Setting breakpoints in the program [ (dbx) stop ] f) Listing the breakpoints that are set [ (dbx) status ] g) Removing a breakpoint [ (dbx) delete ] h) Stepping through the program [ (dbx) step, (dbx) next ] i) Jumping ahead to the next breakpoint [ (dbx) cont ] j) Examining the values of variables [ (dbx) print ] k) Listing a portion of the source code [ (dbx) list ] l) Leaving the debugger [ (dbx) quit ] To use dbx to debug your C programs you need to follows the procedure: 1. Compiling your code for use with the debugger: You must use the -g flag when compiling your code. For example: % cc -g myfile.c will create an a.out executable suitable for dbx. 2. Starting the debugger: Give the 'dbx' command along with the name of the exe- cutable you wish to examine.
    [Show full text]
  • Debugging a Program with Dbx
    Debugging a Program With dbx A Sun Microsystems, Inc. Business 901 San Antonio Road Palo Alto, , CA 94303-4900 Part No: 805-4948 Revision A, February 1999 USA 650 960-1300 fax 650 969-9131 Debugging a Program With dbx Part No: 805-4948 Revision A, February 1999 Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303-4900 U.S.A. All rights reserved. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Portions of this product may be derived from the UNIX® system, licensed from Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the University of California. UNIX is a registered trademark in the United States and in other countries and is exclusively licensed by X/Open Company Ltd. Third-party software, including font technology in this product, is protected by copyright and licensed from Sun’s suppliers. RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions of FAR 52.227-14(g)(2)(6/87) and FAR 52.227-19(6/87), or DFAR 252.227-7015(b)(6/95) and DFAR 227.7202-3(a). Sun, Sun Microsystems, the Sun logo, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
    [Show full text]
  • Using and Porting the GNU Compiler Collection
    Using and Porting the GNU Compiler Collection Richard M. Stallman Last updated 14 June 2001 for gcc-3.0 Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001 Free Software Foundation, Inc. For GCC Version 3.0 Published by the Free Software Foundation 59 Temple Place - Suite 330 Boston, MA 02111-1307, USA Last printed April, 1998. Printed copies are available for $50 each. ISBN 1-882114-37-X Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being “GNU General Public License”, the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled “GNU Free Documentation License”. (a) The FSF’s Front-Cover Text is: A GNU Manual (b) The FSF’s Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. Short Contents Introduction......................................... 1 1 Compile C, C++, Objective C, Fortran, Java ............... 3 2 Language Standards Supported by GCC .................. 5 3 GCC Command Options ............................. 7 4 Installing GNU CC ............................... 111 5 Extensions to the C Language Family .................. 121 6 Extensions to the C++ Language ...................... 165 7 GNU Objective-C runtime features .................... 175 8 gcov: a Test Coverage Program ...................... 181 9 Known Causes of Trouble with GCC ................... 187 10 Reporting Bugs.................................
    [Show full text]
  • Using the GNU Compiler Collection
    Using the GNU Compiler Collection Richard M. Stallman Last updated 20 April 2002 for GCC 3.2.3 Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc. For GCC Version 3.2.3 Published by the Free Software Foundation 59 Temple Place—Suite 330 Boston, MA 02111-1307, USA Last printed April, 1998. Printed copies are available for $50 each. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being “GNU General Public License”, the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled “GNU Free Documentation License”. (a) The FSF’s Front-Cover Text is: A GNU Manual (b) The FSF’s Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Short Contents Introduction ...................................... 1 1 Compile C, C++, Objective-C, Ada, Fortran, or Java ....... 3 2 Language Standards Supported by GCC ............... 5 3 GCC Command Options .......................... 7 4 C Implementation-defined behavior ................. 153 5 Extensions to the C Language Family ................ 157 6 Extensions to the C++ Language ................... 255 7 GNU Objective-C runtime features.................. 267 8 Binary Compatibility ........................... 273 9 gcov—a Test Coverage Program ................... 277 10 Known Causes of Trouble with GCC ...............
    [Show full text]
  • Debugging a Program with Dbx
    Debugging a Program With dbx Forte Developer 7 Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. 650-960-1300 Part No 816-2453-10 May 2002, Revision A Send comments about this document to: [email protected] Copyright © 2002 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries. This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, Forte, Java, Solaris, iPlanet, NetBeans, and docs.sun.com are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
    [Show full text]
  • Oracle® Solaris Studio 12.4: Dbxtool Tutorial 2 > Display Var Will Display 'Var' > Stop in X > Run Running
    ® Oracle Solaris Studio 12.4: dbxtool Tutorial October 2014 Part No: E37084 ■ “Introduction” on page 2 ■ “Example Program” on page 2 ■ “Configuring dbxtool” on page 3 ■ “Diagnosing a Core Dump” on page 9 ■ “Using Breakpoints and Stepping” on page 13 ■ “Using Advanced Breakpoint Techniques” on page 22 ■ “Using Breakpoint Scripts to Patch Your Code” on page 39 Introduction This tutorial uses a “buggy” example program to demonstrate how to use dbxtool, the stand-alone graphical user interface (GUI) for the dbx debugger, effectively. It starts with the basics and then moves on to more advanced features. Example Program This tutorial uses a simplified and somewhat artificial simulation of the dbx debugger. The source code for this C++ program is available in the sample applications zip file on the Oracle Solaris Studio 12.4 downloads web page at http://www.oracle.com/technetwork/server-storage/solarisstudio/ downloads/index.html. After accepting the license and downloading, you can extract the zip file in a directory of your choice. 1. If you have not already done so, download the sample applications zip file, and unpack the file in a location of your choice. The debug_tutorial application is located in the Debugger subdirectory of the SolarisStudioSampleApplications directory. 2. Build the program. $ make CC -g -c main.cc CC -g -c interp.cc CC -g -c cmd.cc CC -g -c debugger.cc CC -g -c cmds.cc CC -g main.o interp.o cmd.o debugger.o cmds.o -o a.out The program is made up of the following modules: cmd.h cmd.cc Class Cmd, a base for implementing debugger commands interp.h interp.cc Class Interp, a simple command interpreter debugger.h debugger.cc Class Debugger, mimics the main semantics of a debugger cmds.h cmds.cc Implementations of various debugging commands main.h main.cc The main() function and error handling.
    [Show full text]
  • Dbx Reference Manual
    dbx Reference Manual IRIS-4D Series SiliconGraphics Computer Systems Document number" 007-0906-030 dbx Reference Manual Version 3.0 Document Number 007-0906-030 12/90 Technical Publications: Wendy Ferguson Beth Fryer Claudia Lohnes Robert Reimann Eng ineering: David Anderson Greg Boyd Jeff Doughty Jim Terhorst © Copyright 1990, Silicon Graphics, Inc. - All rights reserved This document contains proprietary information of Silicon Graphics, Inc. The contents of this document may not be disclosed to third ( parties, copied or duplicated in any form, in whole or in part, without the prior written permission of Silicon Graphics, Inc. Restricted Rights Legend Use, duplication or disclosure of the technical data contained in this document by the Government is subject to restrictions as set forth in subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013, and/or in similar or successor clauses in the FAR, or the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is Silicon Graphics Inc., 2011 N. Shoreline Blvd., Mountain View, CA 94039-7311. dbx Reference Manual Version 3.0 Document Number 007-0906-030 ( Silicon Graphics, Inc. Mountain View, California IRIX and WorkSpace are trademarks and IRIS is a registered trademark of Silicon Graphics, Inc. Contents 1. Introduction • • • • • 1-1 1.1 Using This Manual 1-1 1.2 Conventions • • 1-3 1.3 Relevant Documentation 1-4 2. Getting Started . • • • • 2-1 2.1 Debugging a Simple Program 2-1 2.2 Source-Level Debuggers 2-4 2.3 Activation Levels.
    [Show full text]
  • Programming on Silicon Graphics® Systems: an Overview
    Programming on Silicon Graphics® Systems: An Overview Document Number 007-2476-003 CONTRIBUTORS Written by Eleanor Bassler Edited by C. Kleinfeld Photography by Nancy Cam Production by Heather Hermstad St. Peter’s Basilica image courtesy of ENEL SpA and InfoByte SpA. Disk Thrower image courtesy of Xavier Berenguer, Animatica. © 1998, Silicon Graphics, Inc.— All Rights Reserved The contents of this document may not be copied or duplicated in any form, in whole or in part, without the prior written permission of Silicon Graphics, Inc. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure of the technical data contained in this document by the Government is subject to restrictions as set forth in subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013 and/or in similar or successor clauses in the FAR, or in the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is Silicon Graphics, Inc., 2011 N. Shoreline Blvd., Mountain View, CA 94043-1389. Silicon Graphics, the Silicon Graphics logo, and IRIX are registered trademarks, and IRIS Graphics Library, IRIS IM, IRIS InSight, IconSmith, OpenGL, IRIS ViewKit, POWER Fortran Accelerator, IRIS Performer, Indigo Video, Indy Video, Galileo Video, Indigo2 Video, Sirius Video, ImageVision Library, CASEVision, Impressario, Indigo Magic, Open Inventor, POWER Series, and RealityEngine are trademarks, of Silicon Graphics, Inc. OSF/Motif is a trademark of Open Software Foundation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. X Window System is a trademark of the Massachusetts Institute of Technology.
    [Show full text]
  • Solaris 64-Bit Developer's Guide
    Solaris 64-bit Developer’s Guide Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 816–5138–10 January 2005 Copyright 2005 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
    [Show full text]