HPE NonStop Development Environment for Eclipse 6.0 Debugging Supplement

Transcription

1 HPE NonStop Development Environment for Eclipse 6.0 Debugging Supplement Part Number: Published: June 2016 Edition: L16.05 and subsequent L-series RVUs, J06.20 and subsequent J-series RVUs

2 Copyright 2011, 2016 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. Acknowledgments Microsoft and Windows are trademarks of the Microsoft group of companies. Java and Oracle are registered trademarks of Oracle and/or its affiliates. Warranty Open Software Foundation, OSF, the OSF logo, OSF/1, OSF/Motif, and Motif are trademarks of the Open Software Foundation, Inc. OSF MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED HEREIN, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. OSF shall not be liable for errors contained herein or for incidental consequential damages in connection with the furnishing, performance, or use of this material. 1990, 1991, 1992, 1993 Open Software Foundation, Inc. This documentation and the software to which it relates are derived in part from materials supplied by the following: 1987, 1988, 1989 Carnegie-Mellon University. 1989, 1990, 1991 Digital Equipment Corporation. 1985, 1988, 1989, 1990 Encore Computer Corporation Free Software Foundation, Inc. 1987, 1988, 1989, 1990, 1991 Hewlett-Packard Company. 1985, 1987, 1988, 1989, 1990, 1991, 1992 International Business Machines Corporation. 1988, 1989 Massachusetts Institute of Technology. 1988, 1989, 1990 Mentat Inc Microsoft Corporation. 1987, 1988, 1989, 1990, 1991, 1992 SecureWare, Inc. 1990, 1991 Siemens Nixdorf Informationssysteme AG. 1986, 1989, 1996, 1997 Sun Microsystems, Inc. 1989, 1990, 1991 Transarc Corporation. This software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the University of California. Export of the information contained in this publication may require authorization from the U.S. Department of Commerce.

3 Contents About this document...5 Supported release version updates (RVUs)...5 Intended audience...5 New and changed information...5 Publishing history...6 Change bar notation Introduction...7 Introducing the debugging features for the HPE NonStop Development Environment for Eclipse Debugging tasks...8 Preparing to debug a NonStop Application...8 Related topics...8 Debugging optimized code...8 Preparing to launch a NonStop Application for debugging...9 Specifying program-initiated launch preferences...10 Related topics...12 Attaching the debugger to a NonStop process...13 Related topics...13 Detaching the debugger from a NonStop process...13 Related topics...14 Debugging a Snapshot file...14 Related topics...14 Creating or modifying debug configurations...15 NonStop Application debug configurations...15 NonStop Attach Process debug configurations...22 NonStop Snapshot debug configurations...26 NonStop TS/MP Server configurations...29 Tasks common to all debug configurations...34 Using the debug perspective for NonStop Applications...40 Inspecting the stack...41 Controlling the execution of a NonStop Application...41 Setting watchpoints...42 Setting watch expressions...42 Setting breakpoints...43 Inspecting and modifying variable values...44 Inspecting and modifying register values...45 Inspecting segments...48 Inspecting and modifying memory...49 Inspecting module attributes...50 Inspecting open files...51 NonStop Signals...52 Debugging NonStop applications using Native Inspect (einspect/xinspect) commands...53 Ending a debugging session Reference information...56 Debug perspective for NonStop debugging configurations...56 Debug configurations dialog for NonStop debugging configurations...57 Configurations list...58 Debug configuration group box...59 Main tab...59 TS/MP Server tab...61 Arguments tab...62 Environment tab...63 Contents 3

4 Debugger tab...64 Source tab...64 Common tab for NonStop debug configurations...67 Native Inspect commands supported by NSDEE...67 Related topics...68 NonStop icons and buttons Support and other resources...70 Accessing Hewlett Packard Enterprise Support...70 Accessing updates...70 Websites...70 Related documents...71 Customer self repair...71 Remote support...71 Documentation feedback...71 A VI task mapping...73 Index Contents

5 About this document This manual describes how to use the debugging features of the HPE NonStop Development Environment Version 6.0 for Eclipse (NSDEE). Supported release version updates (RVUs) This document supports: NSDEE 6.0 and all subsequent versions of NSDEE until otherwise indicated in a replacement publication. L16.05 and subsequent L-series RVUs, J06.20 and subsequent J-series RVUs. The Native Inspect (einspect) debugger in J06.19 and all subsequent J-series RVUs until otherwise indicated in a replacement publication. IMPORTANT: J-series RVUs. Program-initiated debug launches are only supported in J06.19 and later The Native Inspect (xinspect) debugger in L15.02 and all subsequent L-series RVUs until otherwise indicated in a replacement publication. Intended audience This document is intended for developers who want to debug NonStop TNS/E and TNS/X native applications, Snapshots, or processes. New and changed information Product changes for NSDEE 6.0 include: Upgrade to Eclipse Mars and CDT 8.8 Support for Windows 7 x86/x64, Windows 8 x86/x64, and Windows 10 x86/x64 Support for Red Hat Enterprise Linux Server release 6.4 (Santiago) Support for Java 7 (JRE 1.7) and Java 8 (JRE 1.8) Support for debugging TS/MP server class applications NonStop Signals view Support for user-defined register groups Variables and Expressions view Cast to NonStop data type adds SPI and EMS buffer formatting Modules view: Support for manual refresh Support for loading symbol files Source lookup using Expand path names Supported release version updates (RVUs) 5

6 Publishing history Part Number R Product Version NSDEE 2.1 NSDEE 4.0 NSDEE 5.0 NSDEE 5.0 NSDEE 6.0 Publication Date February 2011 October 2013 February 2015 November 2015 June 2016 Change bar notation Change bars are used to indicate substantive differences between this manual and its preceding version. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE). The CRE has many new message types and some new message type codes for old message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. 6

7 1 Introduction Introducing the debugging features for the HPE NonStop Development Environment for Eclipse The debugging features for the HPE NonStop Development Environment Version 6.0 for Eclipse (NSDEE) allow you to debug NonStop TNS/E and TNS/X applications developed using NSDEE as well as applications developed outside of NSDEE, attach the debugger to a running process, and debug Snapshot files. The features described in this document are extensions to the Eclipse Workbench, the C/C++ Development Toolkit (CDT), and the NonStop Development Environment Version 6.0 for Eclipse (NSDEE), and use the Native Inspect (einspect/xinspect) debugger. To debug TNS or TNS/R applications, use Inspect or Visual Inspect. The Inspect debugger is available on all NonStop systems. Visual Inspect is an Independent Product that provides graphical debugging capabilities for NonStop Integrity and earlier generation of servers. Supported application programming languages: C and C++ COBOL ptal To debug Java applications for NonStop server targets, see the white paper Using the Eclipse Platform to debug Java applications on HPE NonStop servers at nonstop-docs. For information about the supported versions of NSDEE and Native Inspect, see Supported release version updates (RVUs) (page 5). The NonStop Development Environment for Eclipse 6.0 Debugging Supplement and the NonStop Development Environment for Eclipse 6.0 User Guide are available online from the NonStop Technical Library at: Under User guide, scroll down to NonStop Development Environment for Eclipse 6.0 Debugging Supplement and NonStop Development Environment for Eclipse 6.0 User Guide. This document describes only those features and considerations that are specific to NonStop Applications, Snapshots, and processes. This document is a supplement to the following documents, all of which are available from the Eclipse Workbench help menu. NonStop Development Environment for Eclipse 6.0 User Guide Workbench User Guide C/C++ Development User Guide To access the Workbench help menu, select Help Help Contents. In addition, some users might find these documents helpful: Native Inspect Manual Guardian Programmer's Guide TACL Reference Manual Open System Services User's Guide These documents are available in the NonStop Technical Library at: Introducing the debugging features for the HPE NonStop Development Environment for Eclipse 7

8 2 Debugging tasks Preparing to debug a NonStop Application The standard process to prepare to debug a NonStop Application is: Create a NonStop Local project or NonStop Remote project for the application NOTE: Eclipse workspaces are containers for organizing a set of related projects. Hewlett Packard Enterprise recommends that you use separate workspaces for: Local NSDEE projects and remote NSDEE projects Each application If your workspace combines multiple applications, Hewlett Packard Enterprise recommends that you clear all breakpoints and watch expressions before you debug each application. Build a debuggable version of your application so that you can step through source and examine symbols For information about these tasks, see the NonStop Development Environment for Eclipse 6.0 User Guide. NOTE: NSDEE also supports debugging applications built outside of NSDEE, referred to in this document as projectless debugging. Before you can debug a NonStop Application, you must build a debuggable version of your application so that you can step through the source and examine symbols. For information, see the NonStop Development Environment for Eclipse 6.0 User Guide and Debugging optimized code (page 8). Related topics Related tasks: Preparing to launch a NonStop Application for debugging (page 9) Attaching the debugger to a NonStop process (page 13) Specifying program-initiated launch preferences (page 10) Debugging a Snapshot file (page 14) Debugging optimized code If the application or any project it references has been compiled at an optimization level 1, the Variables view might not be able to display the values of all local variables each time your application is suspended. Figure 1 (page 9), which contains an example of the Variables view for an application compiled at optimization level 1, shows the most common message displayed for a variable that is unavailable due to code optimization: Value not available at the current location 8 Debugging tasks

9 Figure 1 Sample variables view for optimized application In addition to the messages shown in the Variables view, you might see messages similar to these in the Native Inspect (einspect/xinspect) console in the Console view: Value is not available at current location Due to optimization, the address/value of "total" is unknown for the current location. Closest location(s) where it is available: 1) 0x70000e92 to 0x70000ea0 (in line 34) in register $r40 2) 0x70000ea1 to 0x70000ed0 (in line 35) in register $r8 3) 0x70000ef1 to 0x70000f31 (in line 38 to 40) in register $r25 These messages can provide hints about registers that might contain the value of a variable that has a value that can not be displayed in the Variables view due to optimization. If you are having difficulty debugging the application at optimization level 1, you can compile the application at optimization level 0. When you have finished debugging, you can compile the application at higher optimization levels. For more information about code optimization, see the reference manual for the programming language you are using for this application and the Code Profiling Utilities Manual. Preparing to launch a NonStop Application for debugging Before you can debug a NonStop Application using NSDEE, you must select or create a NonStop Application debug configuration. A debug configuration defines how an executable file is to be opened under debugger control. If you want to reuse an existing NonStop Application debug configuration and do not need to modify it, in the Debug Configurations dialog, in the configurations list, select the debug configuration you want to use and double-click to launch it. TIP: If the configurations list contains a large number of debug configurations, find the one you want to select by filtering the results as described in Listing and filtering debug configurations (page 34). To create a new NonStop Application debug configuration, see Creating a new NonStop Application debug configuration (page 15). To modify an existing NonStop Application debug configuration, see Modifying an existing NonStop Application debug configuration (page 17). To specify options for the debugger, enter the information in the Debugger tab. See Specifying debugger options (page 38). NOTE: Often you can access wizards, dialogs, and actions using more than one method. For information about other methods for accessing a wizard or dialog, see the reference topic for that wizard or dialog. Preparing to launch a NonStop Application for debugging 9

10 Specifying program-initiated launch preferences NSDEE 6.0 supports program-initiated debug session launches. The following sections describe how to enable program-initiated launches, specify options, and specify configurations. IMPORTANT: Enabling program-initiated launches allows NSDEE to handle all debug sessions started on the target NonStop system over connections from the Windows client on which NSDEE is running. This includes any debug sessions launched by other instances of NSDEE. Visual inspect can also receive debug sessions that are launched by NSDEE. When using the program-initiated launch feature, you should only connect to a particular NonStop system with a single instance of either NSDEE or Visual Inspect. Program-initiated launch options When a program-initiated debug session is detected, NSDEE creates or reuses a debug configuration that matches the incoming debug launch. To make NSDEE open the Debug Configurations dialog before starting the debug session, use the preference in Windows Preferences Run/Debug Launching Program-initiated Launch Options. Verify the option Open debug configuration before starting debug session is checked. See Figure 2 (page 10). This option is a global setting that applies to all program-initiated launches handled by NSDEE. This option is checked by default. Figure 2 Program-initiated launch options When the Debug Configurations dialog is automatically opened, changes can be made on the Source and Debugger tabs, or the configuration name can be changed on the Main tab. Other changes have no effect on the debug launch in progress. Click Debug to start the debug session. Click Close to transfer the debug launch to Native Inspect on the user s terminal. If this preference is not checked, the debug session is started and the Debug Configurations dialog is not opened. 10 Debugging tasks

11 Network connections To enable program-initiated debug launches, click Windows Preferences NonStop Development Network Connections. Complete the system and user information. Check Accept incoming program-initiated debug connections. See Figure 3 (page 11). Figure 3 Network connections Click Connect to start a server connection to the NonStop system. This option is enabled when the remote system is disconnected as indicated by Status: not connected. This option is disabled when the remote system is connected. To stop the server connection, click Disconnect. When a server connection is started for a host/user, debugging sessions launched by the user on that host are launched in NSDEE. This includes debugging sessions launched with the TACL commands rund, runv, run with the DEBUG option, and the OSS command run debug. It also includes debugging sessions launched by programs that call DEBUG() or PROCESS_DEBUG_(). This option setting is unique for each host/user pair, and is preserved when NSDEE is stopped and restarted. After NSDEE is connected, the user can log on to the NonStop host outside of NSDEE and start a debug session which automatically launches in NSDEE. If the Open debug configuration before starting debug session option is checked, the launch configuration can be reviewed and edited. See Figure 2 (page 10). Preparing to launch a NonStop Application for debugging 11

12 Launch configuration selection For incoming program-initiated debug connections that match more than one saved configuration, a Launch Configuration Selection dialog appears. The list of matching configurations is displayed as a filtered list in a selection dialog. Select a configuration and click OK. Either the Debug Configuration dialog for the selected configuration appears or the debug session is launched, depending on the preference settings. If the user closes the Launch Configuration Selection dialog by clicking the X instead of clicking OK, NSDEE ignores the saved configurations and creates a new configuration for the current debug launch. Figure 4 Launch configuration selection Related topics Related tasks: Creating a new NonStop Application debug configuration (page 15) Modifying an existing NonStop Application debug configuration (page 17) Attaching the debugger to a NonStop process (page 13) Debugging a Snapshot file (page 14) Using the debug perspective for NonStop Applications (page 40) Related reference topics: Debug configurations dialog for NonStop debugging configurations (page 57) Debug perspective for NonStop debugging configurations (page 56) 12 Debugging tasks

13 Attaching the debugger to a NonStop process As an alternative to debugging an application by launching the application under debugger control, you can attach the debugger to a NonStop process. You might want to use this method in these situations: When it is difficult to start the process from the debugger, such as when the process is started in a Guardian Pathway environment. When you need more complex or different terminal emulation than the emulation provided by NSDEE console. To attach the debugger to a NonStop process, you must select or create a NonStop Attach Process debug configuration: If you want to reuse an existing NonStop Attach Process debug configuration, you must modify it to specify CPU and PID. Then click Debug to launch it. TIP: If the configurations list contains a large number of debug configurations, find the one you want to select by filtering the results as described in Listing and filtering debug configurations (page 34). To create a new NonStop Attach Process debug configuration, see Creating a new NonStop Attach Process debug configuration (page 22). To modify an existing NonStop Attach Process debug configuration, see Modifying an existing NonStop Attach Process debug configuration (page 25). To specify options for the debugger, enter the information in the Debugger tab. See Specifying debugger options (page 38). NOTE: Often you can access wizards, dialogs, and actions using more than one method. For information about other methods for accessing a wizard or dialog, see the reference topic for that wizard or dialog. Related topics Related tasks: Creating a new NonStop Attach Process debug configuration (page 22) Modifying an existing NonStop Attach Process debug configuration (page 25) Specifying debugger options (page 38) Ending a debugging session (page 55) Using the debug perspective for NonStop Applications (page 40) Related reference topics: Debug configurations dialog for NonStop debugging configurations (page 57) Debug perspective for NonStop debugging configurations (page 56) Detaching the debugger from a NonStop process To detach the debugger from a process without terminating the process, use one of these methods: In the Debug view, click (Disconnect). From the main toolbar, select Run Disconnect Attaching the debugger to a NonStop process 13

14 Related topics Related tasks: Attaching the debugger to a NonStop process (page 13) Ending a debugging session (page 55) Related reference topics: Debug perspective for NonStop debugging configurations (page 56) The discussion of Debug views in the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) Debugging a Snapshot file A process Snapshot file or Snapshot is a disk file that is an image of a process, its data, and its status at the moment it was saved. Snapshot files are analogous to core files on UNIX systems. Snapshot files have file code 130. The ability to examine a Snapshot file can be useful when a process terminates abnormally and you want to determine the circumstances in effect at the time of the termination. You cannot execute any commands that would alter the state of the Snapshot, or commands that would execute a process, such as step or continue. Such commands report an error during Snapshot analysis. To debug a NonStop Snapshot file, you must select or create a NonStop Snapshot debug configuration: If you want to reuse an existing NonStop Snapshot debug configuration and do not need to modify it, in the Debug Configurations dialog, in the configurations list, select the debug configuration you want to use and double-click to launch it. TIP: If the configurations list contains a large number of debug configurations, find the one you want to select by filtering the results as described in Listing and filtering debug configurations (page 34). To create a new NonStop Snapshot debug configuration, see Creating a NonStop Snapshot debug configuration (page 26). To modify an existing NonStop Snapshot debug configuration, see Modifying an existing NonStop Snapshot debug configuration (page 28). NOTE: Often you can access wizards, dialogs, and actions using more than one method. For information about other methods for accessing a wizard or dialog, see the reference topic for that wizard or dialog. Related topics Related tasks: Creating a NonStop Snapshot debug configuration (page 26) Modifying an existing NonStop Snapshot debug configuration (page 28) Specifying debugger options (page 38) Using the debug perspective for NonStop Applications (page 40) Related reference topics: Debug configurations dialog for NonStop debugging configurations (page 57) Debug perspective for NonStop debugging configurations (page 56) 14 Debugging tasks

15 Creating or modifying debug configurations This topic describes how to create or modify debug configurations using the Debug Configurations dialog for these debug configurations: NonStop Application debug configurations (page 15) NonStop Attach Process debug configurations (page 22) NonStop Snapshot debug configurations (page 26) NonStop TS/MP Server configurations (page 29) In addition, Tasks common to all debug configurations (page 34) describes tasks you can perform using the Debug Configurations for any of the three debug configurations listed above. NonStop Application debug configurations Creating a new NonStop Application debug configuration To debug an application for the first time, you must create a NonStop application debug configuration for this application. NOTE: For program-initiated debugging, you do not have to create a debug configuration first. NSDEE creates one which can then be chosen or modified. For information, see Specifying program-initiated launch preferences (page 10). 1. From the main toolbar, select Run Debug configurations. The Debug Configurations dialog appears. The list in the left side of the Debug Configurations dialog shows the types of debug configurations you can create in addition to the names of debug configurations that have already been created in this workspace. Figure 5 Debug configurations dialog box with Main tab for NonStop Application debug configurations Creating or modifying debug configurations 15

16 2. In the list left side of the Debug Configurations dialog, double-click the NonStop Application configuration type. A new debug configuration appears below the debug configuration type with the default name New_configuration. In the next steps in this procedure, use the tabs on the right side of the Debug Configurations dialog (see Figure 5 (page 15)) to edit your new configuration. When you finish entering the information for each tab, click Apply to apply your changes or Revert to revert to the settings in effect the last time changes were applied, or go on to the next tab and click Apply when you are ready to apply your changes to all tabs. If the Debug button is available and you click Debug, your changes are applied before the debugger is launched. TIP: If you already have configured another NonStop Application debug configuration, you can copy it and modify the copy to create your new NonStop Application debug configuration. However, that debug configuration must already have the correct launch type. 3. In the Name box, enter a name for this debug configuration, or use the default name, New_configuration. 4. In the Main tab, configure these settings: a. For NonStop launch type select Guardian if your application is a Guardian application or select OSS if your application is an OSS application. b. For NonStop project specify the NonStop development project that was used to build the application. Enter the name of the project in the box or click Browse to locate and select the project using the Project selection dialog (page 60). This is optional for applications built outside of NSDEE. c. For NonStop system specify the system on which to run the application. Choose a previously-configured system by selecting a system from the drop-down list, or configure a new system by clicking Edit and using the Configure Connections dialog to configure the remote connection. For more information about the Configure Connections dialog, see the NonStop Development Environment for Eclipse 6.0 User Guide. d. For NonStop executable's path on NonStop system specify the path to the executable file to be debugged on the NonStop system. Enter the full path and name of the executable file, or if you have selected a system in NonStop system, you can click Browse to locate and select the executable file on that remote system. e. If you need to transfer the executable file from your desktop to the NonStop system before you begin debugging, in Local executable to be transferred to NonStop path specified above enter the full path to the executable file on your local system in the box or click Browse to locate and select the file. 5. Optional: If you want to specify options to be used by the run command when launching your program, specify program arguments, or use a working directory other than your home directory. Enter the information in the Arguments tab. See Specifying arguments for NonStop Application debug configurations (page 18). 6. Optional: If you want to specify environment options, such as ASSIGNs, DEFINEs, or PARAMs for Guardian applications or environment variables for OSS applications, enter the information in the Environment tab: If this is a Guardian launch type, see Specifying DEFINEs, ASSIGNs, and PARAMs for Guardian launch types (page 20). If this is an OSS launch type, see Specifying environment variables for OSS launch types (page 21). 7. Optional: If you want to specify options for the debugger to use, enter the information in the Debugger tab. See Specifying debugger options (page 38). 16 Debugging tasks

17 8. Optional: By default, the debugger searches for source files at the path recorded when the application was compiled. If you need to specify a different location, such as when you have moved the files to a different system, use the Source tab to specify the current location of the files. A rule must be specified, either the default or alternate locations. See Specifying alternate source file locations (page 35). 9. Optional: In the Common tab, you can set other options related to the Eclipse workspace. For information about this tab, see Common tab for NonStop debug configurations (page 67). 10. If you have not already done so for each tab, click Apply to apply your changes. To revert to the settings in effect the last time changes were applied, click Revert. Modifying an existing NonStop Application debug configuration To modify an existing NonStop Application debug configuration: 1. From the main toolbar, select Run Debug configurations. The Debug Configurations dialog appears (Figure 5 (page 15)). The list in the left side of the Debug Configurations dialog shows the types of debug configurations you can create in addition to the names of debug configurations that have already been created in this workspace. 2. In the list in the left side of the Debug Configurations dialog, double-click the debug configuration you want to modify. TIP: If the configurations list contains a large number of debug configurations, find the one you want to select by filtering the results as described in Listing and filtering debug configurations (page 34). 3. If you want to change the name of this configuration, enter the new name in the Name box. 4. Make the modifications you want in each of the tabs. When you finish entering the information for each tab, click Apply to apply your changes or Revert to revert to the settings in effect the last time changes were applied, or go on to the next tab and click Apply when you are ready to apply your changes to all tabs. If the Debug button is available and you click Debug, your changes are applied before the debugger is launched. a. In the Main tab, specify the NonStop launch type, project name (optional), system and user name, and the process. If the launch type is modified, also modify the remote path map (if specified) by deleting the old entry and adding a new entry. See Creating a new NonStop Application debug configuration (page 15). b. If you want to specify options to be used by the run command when launching your program, specify program arguments, or use a working directory other than your home directory, enter the information in the Arguments tab. See Specifying arguments for NonStop Application debug configurations (page 18). c. If you want to specify environment options, such as ASSIGNs, DEFINEs, or PARAMs for Guardian applications or environment variables for OSS applications, enter the information in the Environment tab: If this is a Guardian launch type, see Specifying DEFINEs, ASSIGNs, and PARAMs for Guardian launch types (page 20). If this is an OSS launch type, see Specifying environment variables for OSS launch types (page 21). d. If you want to specify options for the debugger to use, enter the information in the Debugger tab. See Specifying debugger options (page 38). e. By default, the debugger searches for source files at the path recorded when the application was compiled. If you need to specify a different location, such as when you have moved the files to a different system, use the Source tab to specify the current Creating or modifying debug configurations 17

18 location of the files. A rule must be specified, either the default or alternate locations. See Specifying alternate source file locations (page 35). f. In the Common tab, you can set other options related to the Eclipse workspace. For information about this tab, see Common tab for NonStop debug configurations (page 67). 5. If you have not already done so for each tab, click Apply to apply your changes. To revert to the settings in effect the last time changes were applied, click Revert. Related topics Related tasks: Creating or modifying debug configurations (page 15) Related reference topics: Debug configurations dialog for NonStop debugging configurations (page 57) Specifying arguments for NonStop Application debug configurations You use the Arguments tab (Figure 6 (page 18)) to specify options to be used by the run command when your program is launched, arguments to pass to the application, and to specify a working directory other than your home directory. Figure 6 Arguments tab for NonStop Application debug configurations 18 Debugging tasks

19 1. To specify arguments for the run command used to launch the application under debugger control, enter them in the box below Run command options (newlines treated as spaces). The syntax used for these arguments must be valid for the option selected for NonStop launch type in the Main tab; either OSS or Guardian. For the Guardian launch type, you are not required to use opening and closing forward slashes. NSDEE does not validate this syntax. This example shows run command arguments, all on the same line, for an application that has an OSS launch type: -gpri=149 -cpu=2 This example shows run command arguments, each on a separate line, for an application that has an OSS launch type: -gpri=149 -cpu=2 This example shows run command arguments, all on the same line, for an application that has a Guardian launch type. The opening and closing slashes (/) are optional: /PRI 149, CPU 2/ This example shows run command arguments, each on a separate line, for an application that has a Guardian launch type. The opening and closing slashes (/) have been omitted (they are optional): PRI 149, CPU 2 NOTE: The debug, nowait, and term options are not supported. You can use the cpu option to specify on which processor the application and the debugger should run. If you specify this option, it is used for both the debugger and the target application. If you do not use the cpu option, the application and debugger are run in a processor that is chosen by the system. 2. To specify arguments to pass to the application, enter them in the box below Program arguments (newlines treated as spaces). The syntax used for these arguments must be valid for the program being debugged. NSDEE does not validate this syntax. 3. By default, your home directory is used as the working directory. To specify a directory other than your home directory: For OSS launch types, select Set working directory. For Guardian launch types, select Set initial $volume.subvolume. Enter the full path and directory name in the box or click Browse to locate and select the directory or volume and subvolume you want to use. 4. Click Apply to apply your changes. To revert to the settings in effect the last time changes were applied, click Revert. Considerations For run command options and program arguments: You can enter program and run command arguments one per line for easy reading or you can enter all of the arguments on a single line, but the syntax you use must be valid for the option selected under NonStop launch type in the Main tab; either OSS or Guardian. NSDEE does not validate this syntax. For the Guardian launch type, you are not required to use opening and closing forward slashes. Creating or modifying debug configurations 19

20 Specifying DEFINEs, ASSIGNs, and PARAMs for Guardian launch types You can specify DEFINEs, ASSIGNs, and PARAMs for Guardian launch types using the Environment tab (Figure 7 (page 20)) of the Debug Configurations dialog. These settings are used for this debug configuration only (they are not stored in your TACLCSTM file, for example). To specify DEFINEs, ASSIGNs, and PARAMs manually, select Set the following DEFINEs, ASSIGNs, and PARAMs and enter them in the box. Separate entries by entering each on its own line. If you would like to use a set of DEFINEs, ASSIGNs, and PARAMs that are stored in a file, you can select Set DEFINEs, ASSIGNs, and PARAMs contained in remote file and either enter the full path and name of the file in the box or click Browse to locate and select the file. NOTE: Enter DEFINEs, ASSIGNs, and PARAMs exactly as you would enter them at the TACL prompt. For example: PARAM TRACE ON ASSIGN STDERR, file-name ADD DEFINE =PLUTO, FILE \FAR.$OFF.WORLDS.PLUTO TIP: You can also cut and paste to enter items in this box. This ability can be useful if you want to copy a subset of DEFINEs, ASSIGNS, and PARAMs from a file or from another debug configuration. For introductory information about DEFINEs, ASSIGNs, and PARAMs, see the TACL Reference Manual and the Guardian Programmer's Guide in the NonStop Technical Library. Figure 7 Environment tab for NonStop Application debug configurations, Guardian launch type 20 Debugging tasks

21 Specifying environment variables for OSS launch types You can specify OSS environment variables for OSS launch types using the Environment tab (Figure 8 (page 22)) of the Debug Configurations dialog. These environment variables are used only for the shell session used with this debug configuration (they are not stored in your.profile file, for example). To specify environment variables manually, select Set the following environment variables and enter them in the box exactly as you would if you were setting the environment variable in the shell. Environment variables generally are in the format export name=value. Separate variables by entering each variable on its own line. If you would like to use a set of environment variables that are stored in a file, you can select Set environment variables contained in remote file and either enter the full path and name of the file in the box or click Browse to locate and select the file. NOTE: Enter environment variables exactly as you would set them in a shell. For example, if you set the environment variable TESTMODE by entering: TESTMODE=1 your setting will not be available to your application. Instead, you must enter: export TESTMODE=1 TIP: You can also cut and paste to enter a set of variables and values in this box. This ability can be useful if you want to copy a subset of variables and values from a file or from another debug configuration. For introductory information about OSS environment variables, see the Open System Services User's Guide in the NonStop Technical Library. Creating or modifying debug configurations 21

22 Figure 8 Environment tab for NonStop Application debug configurations, OSS launch type NonStop Attach Process debug configurations Creating a new NonStop Attach Process debug configuration 1. From the main toolbar, select Run Debug configurations. The Debug Configurations dialog appears (Figure 5 (page 15)). The list in the left side of the Debug Configurations dialog shows the types of debug configurations you can create in addition to the names of debug configurations that have already been created in this workspace. 2. In the list in the left side of the Debug Configurations dialog, double-click the NonStop Attach Process configuration type. A new debug configuration appears below the debug configuration type with the default name New_configuration. In the next steps in this procedure, use the tabs on the right side of the Debug Configurations dialog (see Figure 5 (page 15)) to edit your new configuration. When you finish entering the information for each tab, click Apply to apply your changes or Revert to revert to the settings in effect the last time changes were applied, or go on to the next tab and click Apply when you are ready to apply your changes to all tabs. If the Debug button is available and you click Debug, your changes are applied before the debugger is launched. TIP: If you already have configured another NonStop Attach Process debug configuration, you can copy it and modify the copy to create your new NonStop Attach Process debug configuration. However, that debug configuration must already have the correct launch type. 22 Debugging tasks

23 Figure 9 Main tab for NonStop attach process debug configurations 3. In the Name box, enter a name for this debug configuration, or use the default name, New_configuration. 4. In the Main tab, configure these settings: a. For NonStop launch type, select Guardian if your application is a Guardian application or select OSS if your application is an OSS application. b. For NonStop project, specify the NonStop development project that was used to build the application. Enter the name of the project in the box or click Browse to locate and select the project using the Project selection dialog (page 60). This is optional for applications built outside of NSDEE. c. For NonStop system, specify the system on which the process is running. Choose a previously-configured system by selecting a system from the drop-down list, or configure a new system by clicking Edit and using the Configure Connections dialog to configure the remote connection. For more information about the Configure Connections dialog, see the NonStop Development Environment for Eclipse 6.0 User Guide. Creating or modifying debug configurations 23

24 d. For NonStop CPU and process ID number (CPU, PIN), specify the process you want to debug. Enter the processor number in the first box and the process ID number (PIN) in the second box, or click Browse to select a process. If you click Browse: If you selected the Guardian NonStop launch type, the version of the Process Browser dialog in Figure 10 (page 24) appears. In this example, $ZHOME is entered in the process filter, so only rows that contain the text ZHOME are displayed: Figure 10 Process browser dialog for Guardian launch types If you selected the OSS NonStop launch type, the version of the Process Browser dialog in Figure 11 (page 24) appears: Figure 11 Process browser dialog for OSS launch types 24 Debugging tasks

25 To select a process, click in the row that contains the process, then click OK. The process CPU and PIN are displayed in the boxes in the Main tab of the Debug Configurations dialog, and the Process Browser dialog closes. 5. Optional. If you want to specify options for the debugger, enter the information in the Debugger tab. See Specifying debugger options (page 38). 6. Optional. By default, the debugger searches for source files at the path recorded when the application was compiled. If you need to specify a different location, such as when you have moved the files to a different system, use the Source tab to specify the current location of the files. A rule must be specified, either the default or alternate locations. See Specifying alternate source file locations (page 35). 7. Optional. In the Common tab, you can set other options related to the Eclipse workspace. For information about this tab, see Common tab for NonStop debug configurations (page 67). 8. Click Apply to apply your changes. To revert to the settings in effect the last time changes were applied, click Revert. Modifying an existing NonStop Attach Process debug configuration To modify an existing NonStop Attach Process debug configuration: 1. From the main toolbar, select Run Debug configurations. The Debug Configurations dialog appears (Figure 5 (page 15)). The list in the left side of the Debug Configurations dialog shows the types of debug configurations you can create in addition to the names of debug configurations that have already been created in this workspace. 2. In the list in the left side of the Debug Configurations dialog, double-click the debug configuration you want to modify. Creating or modifying debug configurations 25

26 Related topics TIP: If the configurations list contains a large number of debug configurations, find the one you want to select by filtering the results as described in Listing and filtering debug configurations (page 34). 3. If you want to change the name of this configuration, enter the new name in the Name box. 4. Make the modifications you want in each of the tabs. When you finish entering the information for each tab, click Apply to apply your changes or Revert to revert to the settings in effect the last time changes were applied, or go on to the next tab and click Apply when you are ready to apply your changes to all tabs. If the Debug button is available and you click Debug, your changes are applied before the debugger is launched. a. In the Main tab, specify the NonStop launch type, project name (optional), system and user name, and the process. If the launch type is modified, also modify the remote path map (if specified) by deleting the old entry and adding a new entry. See Creating a new NonStop Attach Process debug configuration (page 22). b. If you want to specify options for the debugger, enter the information in the Debugger tab. See Specifying debugger options (page 38). c. By default, the debugger searches for source files at the path recorded when the application was compiled. If you need to specify a different location, such as when you have moved the files to a different system, use the Source tab to specify the current location of the files. A rule must be specified, either the default or alternate locations. See Specifying alternate source file locations (page 35). d. In the Common tab, you can set other options related to the Eclipse workspace. For information about this tab, see Common tab for NonStop debug configurations (page 67). e. If you have not already done so for each tab, click Apply to apply your changes. To revert to the settings in effect the last time changes were applied, click Revert. Related tasks: Detaching the debugger from a NonStop process (page 13) Ending a debugging session (page 55) Creating or modifying debug configurations (page 15) Related reference topics: Debug configurations dialog for NonStop debugging configurations (page 57) NonStop Snapshot debug configurations NonStop Snapshot debug configurations dialog box is used to perform the following actions: Creating a NonStop Snapshot debug configuration (page 26) Modifying an existing NonStop Snapshot debug configuration (page 28) Creating a NonStop Snapshot debug configuration 1. From the main toolbar, select Run Debug configurations. The Debug Configurations dialog box appears. The list in the left side of the Debug Configurations dialog shows the types of debug configurations you can create in addition to the names of debug configurations that have already been created in this workspace. 26 Debugging tasks

27 2. In the list in the left side of the Debug Configurations dialog, double-click NonStop Snapshot configuration type. A new debug configuration appears below the debug configuration type with the default name New_configuration. In the next steps in this procedure, use the tabs on the right side of the Debug Configurations dialog (see Figure 5 (page 15)) to edit your new configuration. When you finish entering the information for each tab, click Apply to apply your changes or Revert to revert to the settings in effect the last time changes were applied, or go on to the next tab and click Apply when you are ready to apply your changes to all tabs. If the Debug button is available and you click Debug, your changes are applied before the debugger is launched. TIP: If you have configured another NonStop Snapshot debug configuration, you can copy it and modify the copy to create your new NonStop Snapshot debug configuration. However, that debug configuration must already have the correct launch type. 3. In the Name box, enter a name for this debug configuration. 4. In the Main tab, configure these settings: a. Select Guardian or OSS to specify the NonStop launch type. Your selection determines what types of remote paths are allowed in all the tabs of the Debug Configuration dialog and all of the dialogs related to browsing the remote system. b. Enter the name of the project in NonStop project box, or click Browse and select the project using the Project selection dialog (page 60) dialog. This is optional for applications built outside of NSDEE. c. Select a previously-configured system from NonStop system drop-down, or configure a new system by clicking Edit and using the Configure Connections dialog to configure the remote connection. For more information about the Configure Connections dialog, see the NonStop Development Environment for Eclipse 6.0 User Guide. d. Enter the full path to the Snapshot file you want to debug in NonStop Snapshot file box or click Browse to locate and select the file. e. If the executable for the program is not in the same location as it was when the Snapshot was taken, select Location of executable (if moved since Snapshot was created) and enter the full path to the executable in the box or click Browse to locate and select the file. f. Click Apply to apply your changes. To revert to the settings in effect the last time changes were applied, click Revert. Creating or modifying debug configurations 27

28 Figure 12 Main tab for NonStop Snapshot debug configurations 5. Optional: If you want to specify options for the debugger, enter the information in the Debugger tab. See Specifying debugger options (page 38). 6. Optional: By default, the debugger searches for source files at the path recorded when the application was compiled. If you need to specify a different location, such as when you have moved the files to a different system, use the Source tab to specify the current location of the files. A rule must be specified, either the default or alternate locations. See Specifying alternate source file locations (page 35). 7. Optional: In the Common tab, you can set other options related to the Eclipse workspace. For information about this tab, see Common tab for NonStop debug configurations (page 67). 8. Click Apply to apply your changes or Revert to revert to the settings in effect the last time changes were applied. Modifying an existing NonStop Snapshot debug configuration To modify an existing NonStop Snapshot debug configuration: 1. From the main toolbar, select Run Debug configurations. The Debug Configurations dialog appears (Figure 5 (page 15)). 2. In the Debug Configurations dialog, in the configurations list, select the debug configuration you want to modify. TIP: If the configurations list contains a large number of debug configurations, find the one you want to select by filtering the results as described in Listing and filtering debug configurations (page 34). 3. If you want to change the name of this configuration, enter the new name in the Name box. 28 Debugging tasks

29 Related topics 4. Make the modifications you want in each of the tabs. When you finish entering the information for each tab, click Apply to apply your changes or Revert to revert to the settings in effect the last time changes were applied, or go on to the next tab and click Apply when you are ready to apply your changes to all tabs. If the Debug button is available and you click Debug, your changes are applied before the debugger is launched. a. In the Main tab (Figure 12 (page 28)), specify the NonStop launch type, project name (optional), system and user name, and the process. If the launch type is modified, also modify the remote path map (if specified) by deleting the old entry and adding a new entry. See Creating a NonStop Snapshot debug configuration (page 26). b. If you want to specify options for the debugger, enter the information in the Debugger tab. See Specifying debugger options (page 38). c. By default, the debugger searches for source files at the path recorded when the application was compiled. If you need to specify a different location, such as when you have moved the files to a different system, use the Source tab to specify the current location of the files. A rule must be specified, either the default or alternate locations. See Specifying alternate source file locations (page 35). d. In the Common tab, you can set other options related to the Eclipse workspace. For information about this tab, see Common tab for NonStop debug configurations (page 67). 5. Click Apply to apply your changes. To revert to the settings in effect the last time changes were applied, click Revert. Related tasks: Creating or modifying debug configurations (page 15) Related reference topics: Debug configurations dialog for NonStop debugging configurations (page 57) NonStop TS/MP Server configurations NonStop TS/MP Server configurations dialog box is used to perform the following actions: Creating NonStop TS/MP Server debug configuration (page 29) Modifying an existing NonStop TS/MP Server debug configuration (page 33) Creating NonStop TS/MP Server debug configuration 1. From the main toolbar, select Run Debug configurations. The Debug Configurations dialog box appears. The list in the left side of the dialog box displays the types of debug configurations you can create. 2. From the list in the left side of the Debug Configurations dialog box, double-click the NonStop TS/MP Server configuration type. A new debug configuration appears below NonStop TS/MP Server configuration type with the default name New_configuration. The following tabs appear on the right side of the Debug Configurations dialog box: Main TS/MP Server Arguments Environment Debugger Creating or modifying debug configurations 29

30 Source Common For more information on Debug Configuration tabs, see Debug configuration group box (page 59). 3. In the Name box, enter a name for the debug configuration, or use the default name New_configuration. 4. In the Main tab, configure the following settings: Figure 13 Debug Configurations dialog for NonStop TS/MP Server a. Select Guardian or OSS option in Set Server Process Type. b. Enter the name of the NonStop development project used to build the application in NonStop project box or click Browse to locate and select the project using the Project selection dialog (page 60). This is optional for applications built outside of NSDEE. c. Select a previously-configured system from the NonStop system list, or click Edit and use Configure Connections dialog to configure a new system. For more information about Configure Connections dialog box, see NonStop Development Environment for Eclipse 6.0 User Guide. d. Enter the path to the executable file to be debugged on the NonStop system in NonStop executable's path (Set Server Program) box. Or, if you have selected a system in NonStop system, click Browse. The Choose Remote Application window appears. Locate and select the executable file on that remote system in the Choose Remote Application window and click OK. 30 Debugging tasks

31 e. Enter the full path to the executable file on your local system in the Local executable to be transferred to NonStop path specified above box, and click Apply. Or, click Browse to locate and select the file, and click Apply. This transfers the executable file from your desktop to the NonStop system before you begin debugging. 5. In the TS/MP Server tab, configure the following settings: Figure 14 TS/MP Server tab a. Enter the Name of the TS/MP server or click Browse and select the desired TS/MP server. b. Specify the following Server Class details for the TS/MP server: Enter the name of the server class in the Name box. Select New or Restart option to specify the status of the server class. If you select Restart option, Delete the server class, if exist. option and Server Attributes fields are disabled. Select Delete the server class, if exist. option. c. Enter the SET SERVER CPUS value. This parameter controls the CPU on which the TS/MP server is launched. The default value is 0. If it is configured using a Guardian script file, the value set on the TS/MP Server tab takes precedence over the value set in the script file. Creating or modifying debug configurations 31

32 d. Select Configure parameters from Add Commands option. Click Add Commands. The Add Server Commands window is displayed. Select the check box corresponding to the desired server attributes. NOTE: The CPUS and MAXSERVERS settings are disabled in Add Server Commands window. Click OK. Or, select Configure parameters using Guardian script file option. Enter the path or click Browse and select the required path. Enter the required file name in Local file to be transferred to Guardian path specified above box or click Browse and select the required file. 6. Optional: To specify options to be used by the run command when launching your program, specify program arguments, or use a working directory other than your home directory. Enter this information in the Arguments tab. For more information about Arguments tab, see Arguments tab (page 62). 7. Optional: To specify environment options, such as ASSIGNs, DEFINEs, or PARAMs for Guardian applications or environment variables for OSS applications, enter the information in the Environment tab. For more information about Environment tab, see Environment tab (page 63). 8. Optional: To specify options for the debugger to use, enter the information in the Debugger tab. For more information about Debugger tab, see Specifying debugger options (page 38). 9. Optional: By default, the debugger searches for source files at the path recorded when the application was compiled. If you need to specify a different location, such as when you have moved the files to a different system, use the Source tab to specify the current location of the files. For more information about Source tab, see Specifying alternate source file locations (page 35). 32 Debugging tasks

33 10. Optional: In the Common tab, set other options related to the Eclipse workspace. For more information, see Common tab for NonStop debug configurations (page 67). 11. If you have not already done so for each tab, click Apply to apply your changes. To revert to the settings in effect the last time changes were applied, click Revert. Modifying an existing NonStop TS/MP Server debug configuration 1. From the main toolbar, select Run Debug configurations. The Debug Configurations dialog box appears. 2. In the configurations list, select the TS/MP debug configuration you want to modify. TIP: If the configurations list contains a large number of debug configurations, find the one you want to select by filtering the results as described in Listing and filtering debug configurations (page 34). 3. To change the name of the configuration, enter the new name in the Name box. 4. Make the desired modifications in each of the tabs as mentioned in Table 1 (page 33). When you finish entering the information for each tab: Click Apply to apply your changes. Click Revert to revert to the settings in effect the last time changes were applied. Go on to the next tab and click Apply when you are ready to apply your changes to all tabs. If the Debug option is available and you click Debug, your changes are applied before the debugger is launched. Table 1 Modifying existing NonStop TS/MP Server debug configuration Tabs in Debug Configurations dialog box Main Procedure In the Main tab, modify the following: Set Server Process Type NonStop project NonStop system If Set Server Process Type is modified, also update the following: NonStop executable's path (SET SERVER PROGRAM). Local executable to be transferred to NonStop path specified above. TS/MP Server Arguments In the TS/MP Server tab, update Name, Server Class, and Server Attribute as desired. For more information, see Creating NonStop TS/MP Server debug configuration (page 29). To modify the options to be used by the run command when launching your program, specify program arguments, or use a working directory other than your home directory, change the information in the Arguments tab. For more information about Arguments tab, see Arguments tab (page 62). Creating or modifying debug configurations 33

34 Table 1 Modifying existing NonStop TS/MP Server debug configuration (continued) Tabs in Debug Configurations dialog box Environment Debugger Source Common Procedure To modify the environment options, such as ASSIGNs, DEFINEs, or PARAMs for Guardian applications or environment variables for OSS applications, change the information in the Environment tab. For more information about Environment tab, see Environment tab (page 63). To modify the options for the debugger to use, change the information in the Debugger tab. For more information, see Specifying debugger options (page 38). By default, the debugger searches for source files at the path recorded when the application was compiled. If you need to specify a different location, such as when you have moved the files to a different system, use the Source tab to specify the current location of the files. In the Common tab, you can set modify options related to the Eclipse workspace. For more information, see Common tab for NonStop debug configurations (page 67). 5. If you have not already done so for each tab, click Apply to apply your changes. To revert to the settings in effect the last time changes were applied, click Revert. Tasks common to all debug configurations Listing and filtering debug configurations To filter the list of debug configurations shown in the configuration list in the Debug Configurations dialog (Figure 5 (page 15)), use any of these methods: Use the filter box to specify text that must be included in the name of the configuration. For example, if you enter NonStop in the filter, only the NonStop debug configuration types are shown. Click to clear the text in the filter box. Click to collapse all expanded debug configurations. Only the debug configuration types are shown. Click to open the Preferences dialog, which is filtered to show only the Run/Debug preferences. For more information about using this dialog, see the Workbench User Guide. Click the filter menu and select an option from the menu. 34 Debugging tasks

35 Related topics Related tasks: Creating or modifying debug configurations (page 15) Related reference topics: Configurations list (page 58) Deleting an existing debug configuration To delete an existing debug configuration shown in the configuration list in the Debug Configurations dialog (Figure 5 (page 15)), use either of these methods: Click the debug configuration to select it, then click (Delete). Right-click the debug configuration and select Delete. Related topics Related tasks: Listing and filtering debug configurations (page 34) Related reference topics: Configurations list (page 58) Specifying alternate source file locations By default, the debugger looks for source files at their compile-time location. If the source files are not available at their compile-time location, you can use the Source tab (page 36)to direct the debugger to search in alternate locations. NOTE: In most cases, the default path is the correct path. You only change entries in the Source tab if you have moved the source files since the application was compiled. Creating or modifying debug configurations 35

36 Figure 15 Source tab The box for Source Lookup Path contains the list of the categories of rules that have been configured for this debug configuration. Initially only the default rule is configured. The default rule is: For NonStop Remote projects and applications built on NonStop servers outside of NSDEE, a Remote Compile-Time File Path, which specifies that the debugger looks for source files on a remote system using compile-time paths.figure 13 (page 30) shows an example for a remote project. For NonStop Local projects and applications built locally outside of NSDEE, a Local Compile-Time File Path, which specifies that the debugger looks for source files using compile-time paths on the local system. The debugger performs source lookups by applying the rules in the Source Lookup Path list, in order. The debugger stops traversing the list when a match is found. You can use the Up and Down buttons to the right of the list to change the order of the rules. Use the Add and Remove buttons to the right of the list to add or remove entries from the list. Select Edit to edit existing entries. Select Restore Default to restore the default setting of a single default rule. 36 Debugging tasks

37 The options in NonStop system (for Remote Path Lookup) specify the NonStop system on which to search for files: Lookup on same system as launch (see Main tab), when selected, specifies that the debugger look for the files on the same system as specified for the debugging configuration on the Main tab. Lookup on system, when selected, specifies that the debugger look for the files on the system specified in the box. To specify a system, select the system in drop-down list or click Edit to specify a different system than those shown in the list. Adding source lookup paths To add an entry to the Source Lookup Path list in the Source tab, click the Add button to the right of the list. The Add Source dialog appears. From this dialog, you can select and add any of the six types of source lookup rules listed in the dialog. Choose which type of rule you want to add. NOTE: Local directories and path mappings are not supported for NonStop remote projects. Remote directories and path mappings are not supported for NonStop local projects. To look for source files in this location The local compile-time location. A local directory that you will specify. On the local system using a path derived by substituting part or all of a file s compile-time path with a replacement path. Select this rule type and click OK Local Compile-Time File Path (This is the default rule for local NonStop projects and applications built locally outside of NSDEE) Local File System Directory Local Path Mapping This happens next The rule you selected is added to the list of source lookup path entries shown in the Source tab. The Add File System Directory dialog is displayed. Follow the instructions in Add file system directory dialog (page 66). A new path mapping entry is added to the list of entries in the Source tab, but this new entry does not have any mappings associated with it. To add path mappings to a path mapping entry, select the path mapping entry in the list in the Source tab and click Edit. The Path Mappings dialog is displayed. Follow the instructions in Creating and editing path mapping lookups (page 37). The remote compile-time location. Remote Compile-Time File Path (This is the default rule for remote NonStop projects and applications built on NonStop servers outside of NSDEE.) The rule you selected is added to the list of source lookup path entries shown in the Source tab. A remote directory that you will specify. On the remote system using a path derived by substituting part or all of a file s compile-time path with a replacement path. Remote File System Directory Remote Path Mapping The Add File System Directory dialog is displayed. Follow the instructions in Add file system directory dialog (page 66). A new path mapping entry is added to the list of entries in the Source tab, but this new entry does not have any mappings associated with it. To add path mappings to a path mapping entry, select the path mapping entry in the list in the Source tab and click Edit. The Path Mappings dialog is displayed. Follow the instructions in Creating and editing path mapping lookups (page 37). Creating and editing path mapping lookups Path mappings tell the debugger to replace part of a source file's compile-time path with another path and to use the resulting path to search for source files. For example, suppose your remote OSS source files were located in /home/mikeb/myproj when you compiled the program, but Creating or modifying debug configurations 37

38 later you moved the sources to /home/mikeb/fy09/myproj. By creating a path mapping of /home/mikeb to /home/mikeb/fy09, you tell the debugger to substitute /home/mikeb/fy09 whenever it looks for a source path that starts with /home/mikeb/. To add path mapping entries to the Source Lookup Path list in the Source tab 1. Create a container for the path mapping entries: a. To the right of the Source Lookup Path list, click Add. The Add Source dialog appears. b. Select either Local Path Mapping or Remote Path Mapping c. Click OK. 2. Add one or more path mappings to the container: a. Select the path mapping container (by default, named either Local Path Mapping New Mapping or Remote Path Mapping New Mapping). b. Click Edit. Depending on the type of mapping you selected, either the Local Path Mappings dialog or the Remote Path Mappings dialog appears. c. (Optional) Change the name of the mapping container by editing the Name box. d. Click Add. If you chose a local path mapping, the Local Path Mapping dialog appears. If you chose a remote path mapping, the Remote Path Mapping dialog appears. e. In Compilation path, enter the portion of the original compile-time path that you want to replace. f. In the box in the bottom, enter replacement path or click Browse to locate and select the system path. g. Click OK to apply your changes and close the dialog. h. Either click OK to apply your changes and close the Local Path Mappings dialog or the Remote Path Mappings dialog. Related topics Related tasks: Creating or modifying debug configurations (page 15) Related reference topics: Source tab (page 64) Specifying debugger options You specify debugger options for a debug configuration using the Debugger tab (Figure 16 (page 39)). 38 Debugging tasks

39 Figure 16 Debugger tab The Use default debugger option is selected by default. To use a different debugger than the default debugger (for example, you have installed a different version of the debugger in another location), select Use debugger at the following path and enter the path in the box or click Browse to locate and select the debugger you want to use. (NonStop Application debug configurations only) By default, Stop at main entry point after launch is selected. To specify a function at which to stop before the main entry point is reached, select Stop at the following function after launch and enter the name of the function in the box. In the Debug Configurations dialog, the Debugger tab includes a checkbox labeled Enable access to privileged code and data. By default, this option is not selected. Select this option to enable debugging of privileged code and data. NOTE: This checkbox does not appear for NonStop Snapshot debug configurations. Creating or modifying debug configurations 39

40 Related topics Related tasks: Creating or modifying debug configurations (page 15) Related reference topics: Debugger tab (page 64) Using the debug perspective for NonStop Applications The Debug perspective for NonStop Applications, Snapshot files, and processes is an extension of the C/C++ Development Toolkit (CDT), and is nearly identical to the CDT Debug perspective. For a brief description of the key differences, see Debug perspective for NonStop debugging configurations (page 56). The following figure shows an example of the Debug perspective being used to debug a NonStop Application. It also lists the For information about the CDT, see the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) Figure 17 Debug perspective for NonStop Applications This topic describes common debugging tasks as they apply to debugging NonStop Applications, Snapshot files, and processes, including: Inspecting the stack (page 41) Controlling the execution of a NonStop Application (page 41) NonStop Signals (page 52) Setting watchpoints (page 42) 40 Debugging tasks

41 Setting watch expressions (page 42) Setting breakpoints (page 43) Inspecting and modifying variable values (page 44) Inspecting and modifying register values (page 45) Inspecting and modifying memory (page 49) Debugging NonStop applications using Native Inspect (einspect/xinspect) commands (page 53) Ending a debugging session (page 55) Inspecting the stack Related topics You can use the Debug view to inspect the stack for NonStop Applications in the same ways that you can use the Debug view in CDT to inspect the stack for other kinds of applications. For more information about this task, see the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) Related reference topics: Debug perspective for NonStop debugging configurations (page 56) See also the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) Controlling the execution of a NonStop Application You can use the Debug view to control the execution of a NonStop Application in the same way that you use the Debug view in the CDT to control the execution of other kinds of applications, including using the Run menu and using the icons in the Debug view. For information about controlling debug execution, see the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) Considerations for NonStop Attach Process debug configurations For NonStop Attach Process debug configurations, selecting Run Terminate or the terminate icon terminates the process to which you attached the debugger. To release the process from debugger control and allow the process to continue executing, select Run Disconnect or, in the Debug view, click (Disconnect). Before disconnecting the debugger from the process, clear all breakpoints in the process and continue process execution. If you attempt to disconnect from a process when breakpoints are set, a warning appears that describes the situation and gives you the option of continuing or aborting the operation. If the process is suspended, it is resumed automatically. Using the debug perspective for NonStop Applications 41

42 Related topics Related tasks: Debugging a Snapshot file (page 14) Related reference topics: Debug perspective for NonStop debugging configurations (page 56) Setting watchpoints Related topics Watchpoints are not supported for NonStop debugging. However, you can use the mab command, which has similar capabilities, in the Native Inspect (einspect/xinspect) console. For more information about the Native Inspect console, see Entering Native Inspect commands from the console view (page 53). For more information about the mab command, see the Native Inspect Manual. Related tasks: Entering Native Inspect commands from the console view (page 53) Setting watch expressions You set watch expressions for NonStop processes in the same ways that you can set watch expressions in the CDT. For information about watch expressions, see the discussion about adding expressions in the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) NOTE: Watch expressions are associated with your Eclipse workspace, not with a particular project. Consequently, if you debug multiple projects in the same workspace, errors can be reported if an expression in your workspace is not valid for the project you are debugging. Hewlett Packard Enterprise recommends that you clear all watch expressions before you debug a different program in the same workspace. In addition, you can configure multiple Eclipse workspaces and use a workspace for each set of related projects. For more information about configuring workspaces, see the NonStop Development Environment for Eclipse User Guide. Casting watch expressions to NonStop data types Use the Expressions view context menu to cast a watch expression to a NonStop data type. 1. To open the context menu, right-click on the Expressions view entry you want to modify. 2. Select Cast To NonStop Data Type. The Cast to NonStop Data Type dialog box appears. Select a type from the drop-down list: Code Location (32-bit address) Code Location (64-bit address) EMS Buffer Julian Timestamp (64-bits) UTC Julian Timestamp (64-bits) LCT Process Handle SPI Buffer System Number 42 Debugging tasks

43 Related topics Timestamp (48 bits) TOS Version 3. Click Ok. The value for that entry is updated to the selected format. To cancel the operation, click Cancel. The Cast to NonStop Data Type selection in the Expressions view context menu changes the type of the selected entry and applies NonStop-specific formatting to the displayed value. NOTE: The value of an expression cast to one of the NonStop OS data types cannot be modified in the Expressions view. Considerations An Expressions view entry cast to a NonStop OS data type is displayed as the selected type if the expression resolves to a valid value of the appropriate type. EMS Buffer, SPI Buffer, Process Handle, and 48-bit Timestamp typecasts are only valid for array and pointer type expressions. If SPR T1237H01^ABI or an earlier debugger is used, an error message (Value not available at current location) is displayed if you cast to NonStop data types. Related reference topics: Debug perspective for NonStop debugging configurations (page 56) See also the discussion about adding expressions in the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) Setting breakpoints Related topics You set and edit breakpoints for NonStop Applications in the same ways that you can set breakpoints in the CDT for other types of applications. For information about breakpoints, see the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) NOTE: Breakpoints are associated with your Eclipse workspace, not with a particular project. Consequently, if you debug multiple projects in the same workspace, errors can be reported if a breakpoint in your workspace is not valid for the project you are debugging. Hewlett Packard Enterprise recommends that you clear all breakpoints before you debug a different program in the same workspace. In addition, you can configure multiple Eclipse workspaces and use a workspace for each set of related projects. For more information about configuring workspaces, see the NonStop Development Environment for Eclipse User Guide. Setting breakpoints is the equivalent of using the Native Inspect break command. Deleting breakpoints is the equivalent of using the Native Inspect delete breakpoints command. NOTE: NSDEE uses sequential line numbers instead of the line numbers established by the EDIT program. Setting breakpoints at fractional EDIT line numbers is not supported. Related reference topics: Debug perspective for NonStop debugging configurations (page 56) See also the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) Using the debug perspective for NonStop Applications 43

44 Inspecting and modifying variable values You can inspect and modify variables for NonStop Applications in the same ways that you can inspect and modify variables using the CDT for other types of applications. For information about inspecting and modifying variables, see the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) NOTE: Casting a variable to a different type is supported for C/C++ applications only. Do not attempt to use NSDEE to cast a variable to a different type in COBOL or ptal applications. For ptal variables, you can cast integer variables to ASCII values by entering the print /c command in the Native Inspect console. For example: > print /c gstartup_message.default $11 = { VOL = {79 "O", 83 "S", 32 " ", 32 " "}, SUBVOL = {65 "A", 66 "B", 84 "T", 32 " "} } Casting variables to NonStop data types Use the Variables view context menu to cast a variable to a NonStop data type. 1. To open the context menu, right-click on the Variables view entry that you want to modify. The Cast to NonStop Data Type dialog box appears. 2. Select a type from the drop-down list. The options are: Code Location (32-bit address) Code Location (64-bit address) EMS Buffer Julian Timestamp (64-bits) UTC Julian Timestamp (64-bits) LCT Process Handle SPI Buffer System Number Timestamp (48 bits) TOS Version 3. Click Ok. The value for that entry is updated to the selected format. To cancel the operation, click Cancel. The Cast to NonStop Data Type selection in the Variables view context menu changes the type of the selected entry and applies NonStop-specific formatting to the displayed value. NOTE: The value of a variable cast to one of the NonStop OS data types cannot be modified in the Variables view. Function return values The Variables view displays the function return value after executing a step-return. The Name field for this entry contains the name of the function followed by returned. 44 Debugging tasks

45 Considerations Related topics The Variables view does not display the function return value after a step-return if one of the following versions of the debugger is used: SPR T1237H01^ABI or earlier versions SPR T0903L02^AAC or earlier versions If the application or any project it references has been compiled at optimization level 1, the Variables view might not be able to display the values of all local variables each time your application is suspended. For more information about variables and optimization, see Debugging optimized code (page 8). When your applications stops at a breakpoint set at a function declaration, the values of the local variables shown in the Variables view are not accurate. However, when you step your application to the function's first statement, the variables in the Variables view are updated with accurate values. Related tasks: Inspecting and modifying register values (page 45) Inspecting and modifying memory (page 49) Specifying debugger options (page 38) Debugging optimized code (page 8) Related reference topics: Debug perspective for NonStop debugging configurations (page 56) Debugger tab (page 64) See also the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) Inspecting and modifying register values The Registers view displays a single group of registers when debugging a TNS/X application. It displays the register values for the frame selected in the Debug view. Prior to NSDEE 5.0, the Registers view always displayed the register values of the topmost frame. Using the debug perspective for NonStop Applications 45

46 Figure 18 Registers view TNS/E 46 Debugging tasks

47 Figure 19 Registers view TNS/X You can inspect and modify register values for NonStop Applications in the same ways that you can inspect and modify register values in the CDT for other types of applications. For information about inspecting and modifying register values, see the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) For information about register names for NonStop TNS/E applications, see the Native Inspect Manual in the NonStop Technical Library. You can define a new register group or restore the view to display only the default register groups. NOTE: Casting a register to a different type is supported for C/C++ applications only. Do not attempt to cast a register to a different type in COBOL or ptal applications. Adding a register group 1. Right-click in Registers view, and select Add Register Group from the context menu. The Register Group dialog box appears. 2. Enter the Group Name. 3. To add register names to the Register Group: Select the check boxes corresponding to the desired register names. Click Select All to add all registers in the list. Click Deselect All to clear all register selections. 4. Click OK. Restoring default register groups To reset Registers view to display only the default register groups, right-click in Registers view window and select Restore Default Register Groups. Using the debug perspective for NonStop Applications 47

48 Related topics Related tasks: Inspecting and modifying variable values (page 44) Inspecting and modifying memory (page 49) Specifying debugger options (page 38) Related reference topics: Debug perspective for NonStop debugging configurations (page 56) Debugger tab (page 64) See also the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) Inspecting segments Segments is a read-only view that displays the current list of memory segments allocated by a NonStop application. Each row in this view lists information for a memory segment. Each row includes four columns: Segment ID Base Size FileName The Segments view also includes a details pane that shows additional segment properties for the selected view entry. These additional segment properties are: Dynamic Selection Size limit Usage Flags Use count The Segments view is updated to show changes to the memory segments and their properties including the detailed properties displayed for the selected entry for the details pane. These view updates occur after the selected program suspends execution. No updates occur while the program is executing. The Segments view is updated when the program stops, but changes to the Segments view entries are not highlighted. To adjust how the details pane is displayed, use the view menu which includes: Vertical Horizontal Automatic Segments View Only Show Columns Select Columns If the Segments view is opened in the Debug perspective, the new view is placed on top right side, along with the other debug views such as Variables and Expressions views. 48 Debugging tasks

49 If the Segments view is opened in any other perspective, the view is placed next to the Console view. In the Debug perspective, the menu selection Windows Reset Perspective adds and properly places the Segments view. If the Segments view is not displayed in the Debug perspective, it can be opened from Windows Show View Other under the Debug folder, or by resetting the perspective with Windows Reset Perspective. Figure 20 Segments view Related topics NOTE: The details pane displays only Selection attribute if SPR T1237H01^ABG or earlier versions of the debugger are used. Related tasks: Specifying debugger options (page 38) Related reference topics: Debug perspective for NonStop debugging configurations (page 56) Debugger tab (page 64) Inspecting and modifying memory Related topics You can inspect and modify memory for NonStop Applications in the same ways that you can inspect and modify memory in the CDT for other types of applications. For information about inspecting and modifying memory, see the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) Related tasks: Inspecting and modifying register values (page 45) Inspecting and modifying register values (page 45) Related reference topics: Debug perspective for NonStop debugging configurations (page 56) Debugger tab (page 64) See also the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) Using the debug perspective for NonStop Applications 49

50 Inspecting module attributes The Modules view displays the following module attributes for the selected module: Type Symbols Symbol file Additional attributes displayed may vary depending on the version of Native Inspect installed on the host system. Native Inspect provides a list of attribute names and values, which NSDEE displays in its entirety. NOTE: The Base Address attribute in NSDEE 4.0 and earlier versions is renamed as the Text Start Address. The Size attribute in NSDEE 4.0 and earlier versions is renamed as Text Size. Figure 21 Modules view In Modules view, right-click on the required entry and select one of the following from the context menu: Select Find to search for an entry in the view. Select Load Symbol File to load symbol information for the selected module. For more information see section Loading symbol file for a module (page 50). Select Unload Symbol File to unload the symbol file associated with the selected module. If a symbol file is not loaded for the selected module, then the Unload Symbol File option is not displayed. Select Refresh to update the load modules displayed for the selected debug session and the attributes displayed in the details pane for the selected module. Loading symbol file for a module 1. In Modules view, right-click on the required entry and select Load Symbol File. The Load Symbol File dialog box appears. 2. In Load Symbol File dialog box enter the symbol file pathname in the box, or click Browse to select the required symbol file. For files launched in Guardian applications the pathname is in $volume.subvolume.file format and for those launched in OSS application the pathname starts with /. 50 Debugging tasks

51 Related topics 3. (Optional) Select read symbols now check box. If this option is selected, the specified symbol information is read immediately. If it is cleared, the debugger determines whether to read symbol information immediately or on-demand. 4. Click Ok to save the symbol file. Considerations If a symbol file is already loaded for the selected module, the Load Symbol File selection causes the current symbol file to be unloaded before a new symbol file is loaded. While using Native Inspect SPR T1237H01^ABI or earlier versions or SPR T0903L02^AAC or earlier versions of the debugger, an error message is displayed if the symbol file name does not match the file name of the selected module. Related tasks: Specifying debugger options (page 38) Related reference topics: Debug perspective for NonStop debugging configurations (page 56) Debugger tab (page 64) Inspecting open files FileOpens is a read-only view that displays the current list of open files for the program selected in the Debug view. Each row in this view lists information for a single open file. Each row includes three columns: FileNum LastErr Name The FileOpens view also includes a details pane that shows additional open file attributes for the selected view entry. The additional attributes displayed in the details pane may vary depending on the version of Native Inspect installed on the host system. Native Inspect provides a list of attribute names and values, which NSDEE displays in its entirety. The FileNum -1 entry is the last attempted file operation not associated with a file number. The name is blank, and the details pane does not show additional properties when it is selected. The FileOpens view is updated to show changes to the open files and their properties including the detailed properties displayed for the details pane for the selected entry. These view updates occur after the selected program suspends execution. No updates occur while the program is executing. The FileOpens view is updated when the program stops, but changes to FileOpens view entries are not highlighted. To adjust how the details pane is displayed, use the view menu which includes: Vertical Horizontal Automatic FileOpens View Only Show Columns Select Columns Using the debug perspective for NonStop Applications 51

52 If the FileOpens view is opened in the Debug perspective, the new view is placed on top right side, along with the other debug views such as Variables and Expressions views. If the FileOpens view is opened in any other perspective, the view is placed next to the Console view. In the Debug perspective, the menu selection Windows Reset Perspective adds and properly places the FileOpens view. The FileOpens view is not displayed in the Debug perspective. It can be opened from Windows Show View Other under the Debug folder, or by resetting the perspective with Windows Reset Perspective. Figure 22 FileOpens view Related topics NOTE: If SPR T1237H01^ABG or earlier versions of the debugger are used, the FileOpens view does not display any attributes in the details pane. Related tasks: Specifying debugger options (page 38) Related reference topics: Debug perspective for NonStop debugging configurations (page 56) Debugger tab (page 64) NonStop Signals You can view the current signal handler settings for the program selected in the Debug perspective using NonStop Signals view. The NonStop Signals view is used to perform the following: Viewing NonStop Signals (page 52) Modifying NonStop Signals (page 53) Viewing NonStop Signals Select Window+Show View+Other+Debug+NonStop Signals. The NonStop Signals view is placed next to Variables view in the Debug perspective or next to Console view in the NonStop Development perspective. Changes to the signal handler settings when a program suspends are reflected in the NonStop Signals view. 52 Debugging tasks

53 Modifying NonStop Signals 1. Select Window+Show View+Other+Debug+NonStop Signals. 2. Right-click on the signal entry you want to modify and select Edit signal handler from the context menu. The Edit Signal Handler dialog appears. 3. Select Signal Action or Native Address. If you select Signal Action, then select one of the following options from the drop-down: SIG_IGN SIG_ABORT SIG_DFL SIG_DBG If you select Native Address, then enter the address of the signal handler function in the text box. 4. Click Ok. Debugging NonStop applications using Native Inspect (einspect/xinspect) commands In addition to the debugging tasks you can perform using the Debug perspective, you can use the Native Inspect (einspect/xinspect) console in the Console view to enter a limited set of Native Inspect debugging commands. For a list of supported Native Inspect commands, see Native Inspect commands supported by NSDEE (page 67). Breakpoints that are added, deleted, or modified by commands entered in the Native Inspect console are reflected in the Breakpoints view. NOTE: NSDEE ignores the Native Inspect configuration file (EINSCSTM on TNS/E and XINSCSTM on TNS/X). You must configure the debugger using the Debug Configurations dialog only. Entering Native Inspect commands from the console view You can enter Native Inspect commands that are supported by NSDEE from the Native Inspect (einspect/xinspect) console in the Console view: 1. If the name of the console does not include einspect or xinspect, click (Console) to change the console that is displayed. 2. Enter commands in the console as you would enter them at a terminal. The Native Inspect console does not display a prompt, but it accepts your commands when you enter them and press the return key. NOTE: NSDEE does not validate this syntax Related topics Related tasks: Switching between the Native Inspect (einspect or xinspect) console and the application console (page 54) Related reference topics: Debug perspective for NonStop debugging configurations (page 56) Native Inspect commands supported by NSDEE (page 67) Using the debug perspective for NonStop Applications 53

54 Switching between the Native Inspect (einspect or xinspect) console and the application console When you launch a NonStop Application debug configuration, there are two consoles in the Console view: The Native Inspect (einspect) console, shows the name einspect after the name of the debug configuration for TNS/E debug sessions. The console title includes "Priv" when privileged debugging is enabled in the debug configuration. The following is an example of the einspect console when privileged debugging is enabled. The Native Inspect (xinspect) console, shows the name xinspect after the name of the debug configuration for TNS/X debug sessions. The console title includes "Priv" when privileged debugging is enabled in the debug configuration. The following is an example of the xinspect console when privileged debugging is not enabled. The application console, which displays the path to the application after the name of the debug configuration: To switch between the consoles, in the Console view, use one of these methods: Click (Console) in the upper right corner of the Console view. Select the console you want to display from the Console view menu:. Select the Native Inspect (einspect/xinspect) console by clicking the Native Inspect node in the Debug view (see Figure 23 (page 57)). Select the application console by clicking the application node in the Debug view (see Figure 23 (page 57)). 54 Debugging tasks

55 Related topics Related tasks: Entering Native Inspect commands from the console view (page 53) Related reference topics: Debug perspective for NonStop debugging configurations (page 56) Ending a debugging session Related topics The debugging session ends when one of these conditions occurs: The application or process being debugged terminates. You click (Terminate) in the Debug view or you select Run Terminate. If you have attached the debugger to a process and you release the process from debugger control by clicking (Disconnect) in the Debug view or selecting Run Disconnect. You exit the Eclipse application. Related tasks: Using the debug perspective for NonStop Applications (page 40) Controlling the execution of a NonStop Application (page 41) Detaching the debugger from a NonStop process (page 13) Using the debug perspective for NonStop Applications 55

56 3 Reference information Debug perspective for NonStop debugging configurations The Debug perspective for NonStop Applications, Snapshot files, and processes is an extension of the C/C++ Development Toolkit (CDT), and is nearly identical to the CDT. Figure 17 (page 40) shows an example of the Debug perspective for NonStop debugging. The key differences from the CDT include: The perspective switcher toolbar includes an icon ( ) for the NonStop Development perspective. For more information about this perspective, see the NonStop Development Environment for Eclipse User Guide. For more information about the perspective switcher toolbar, see the discussion of toolbars in the concepts section of the Workbench User Guide. TIP: You can change the perspective switcher to display icons or both icons and names. Place your cursor over one of the perspectives in the perspective switcher, right-click, and select Show Text. A NonStop debug configuration has the NonStop icon as its label decoration. These are the types of NonStop debug configurations: NonStop Application NonStop Attach Process NonStop Snapshot NonStop TS/MP Server For more information about these debug configurations, see the Debug configurations dialog for NonStop debugging configurations (page 57). The Debug Configurations dialog has features specific to the NonStop debug configurations. See Debug configurations dialog for NonStop debugging configurations (page 57). In the Debug view, the Restart action is not supported. If privileged debugging is enabled, "Priv" appears at the end of the associated einspect or xinspect debug session. The Debug view also shows a Native Inspect (einspect/xinspect) node in addition to the application node (Figure 23). 56 Reference information

57 Figure 23 Debug view for NonStop debugging The Executables view is not supported. In the Variables, Registers, or Expressions views, casting a register or variable to a different type is supported for C/C++ applications only. The Signals view is not supported. Instead, you can use the NonStop Signals view, which has similar capabilities. Setting watchpoints is not supported. Instead, you can use the mab command, which has similar capabilities, in the Native Inspect (einspect/xinspect) console. A running program process cannot start the debugger. For example you cannot call the debugger program from the process. For information about the CDT, see the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help Help Contents.) Debug configurations dialog for NonStop debugging configurations Before you can debug a remote NonStop Application, you must create a debug configuration using the Debug Configurations dialog. You can access this dialog in any of these ways: In the Project Explorer view, right-click and select Debug As Debug Configurations On the main menu bar, select Run Debug Configurations In the main toolbar, also known as the Workbench toolbar, select the Debug view menu icon, then select Debug Configurations Debug configurations dialog for NonStop debugging configurations 57