NonStop Development Environment for Eclipse 7.0 Debugging Supplement

Transcription

1 NonStop Development Environment for Eclipse 7.0 Debugging Supplement Part Number: Published: August 2017 Edition: L15.02 and all subsequent L-series RVUs, J06.18 and all subsequent J-series RVUs

2 Notices 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 either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. UNIX is a registered trademark of The Open Group. Warranty Java and Oracle are registered trademarks of Oracle and/or its affiliates. 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.

3 Export of the information contained in this publication may require authorization from the U.S. Department of Commerce.

4 Contents About this document... 6 Supported release version updates (RVUs)...6 Intended audience... 6 New and changed information for NSDEE Related documents... 7 Publishing history...7 Introduction... 8 Introducing the debugging features for the HPE NonStop Development Environment for Eclipse...8 Debugging tasks... 9 Preparing to debug a NonStop Application...9 Debugging optimized code... 9 Preparing to launch a NonStop Application for debugging Specifying program-initiated launch preferences Specifying Native Inspect settings Switching user...16 Attaching the debugger to a NonStop process Detaching the debugger from a NonStop process...17 Debugging a Snapshot file...18 Creating or modifying debug configurations NonStop Application debug configurations NonStop Attach Process debug configurations...25 NonStop Snapshot debug configurations...29 NonStop TS/MP Server configurations Tasks common to all debug configurations Using the debug perspective for NonStop Applications...43 Inspecting the stack Controlling the execution of a NonStop Application Setting watchpoints Setting watch expressions Setting breakpoints Inspecting and modifying variable values Inspecting and modifying register values Inspecting segments Inspecting and modifying memory Inspecting module attributes Inspecting open files Viewing heap profile report...55 Viewing leak profile report...57 Viewing heap corruption report Heap events Viewing leak report...59 NonStop Signals Debugging NonStop applications using Native Inspect (einspect/xinspect) commands...60 Enabling GDB traces Contents

5 Ending a debugging session Reference information Debug perspective for NonStop debugging configurations...62 Debug configurations dialog for NonStop debugging configurations Configurations list...64 Debug configuration group box Main tab...66 TS/MP Server tab...69 Arguments tab...70 Environment tab Debugger tab Memory tab Source tab...74 Common tab for NonStop debug configurations Native Inspect commands supported by NSDEE NonStop icons and buttons...80 Heap profile report Leak profile report Heap Corruption report Leak report...82 Troubleshooting Invalid rtcdll location...83 rtcdll library is not found Minimum heap size validation error Minimum leak size validation error...84 Switch user name error...84 Block-size value validation error Websites Support and other resources...86 Accessing Hewlett Packard Enterprise Support Accessing updates...86 Customer self repair...87 Remote support Warranty information...87 Regulatory information...88 Documentation feedback VI task mapping...89 Contents 5

6 About this document This manual describes how to use the debugging features of the HPE NonStop Development Environment Version 7.0 for Eclipse (NSDEE). Supported release version updates (RVUs) This document supports: NSDEE 7.0 and all subsequent versions of NSDEE until otherwise indicated in a replacement publication. L15.02 and all subsequent L-series RVUs, J06.18 and all 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: Program-initiated debug launches are only supported in J06.19 and later J-series RVUs. 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 for NSDEE 7.0 Added the following sections: Specifying Native Inspect settings on page 14 NI Settings parameters on page 15 Switching user on page 16 Specifying memory options on page 38 Viewing heap profile report on page 55 Viewing leak profile report on page 57 Viewing heap corruption report on page 58 Heap events on page 59 Viewing leak report on page 59 Enabling GDB traces on page 60 Memory tab on page 73 Heap profile report on page 81 Leak profile report on page 81 Heap Corruption report on page 81 Leak report on page 82 Troubleshooting on page 83 Updated the following sections: Added Switch user option in Network connections on page 12. Added Memory tab in Creating a new NonStop Application debug configuration on page 19 and Modifying an existing NonStop Application debug configuration on page About this document

7 Added NonStop Process options in the Main tab and Memory tab in Creating a new NonStop Attach Process debug configuration on page 25 and Modifying an existing NonStop Attach Process debug configuration on page 28. NonStop TS/MP Server configurations on page 32 Creating NonStop TS/MP Server debug configuration on page 32 Added Load Symbols For All option in Inspecting module attributes on page 52 and Loading symbol file for a module on page 53. Added memory tab in Debug configuration group box on page 65. Related documents This document supplements these documents, all of which are available from the Eclipse Workbench help menu. Select Help > Help Contents: NonStop Development Environment for Eclipse 7.0 User Guide Workbench User Guide C/C++ Development User Guide In addition, some readers might find these documents helpful: Native Inspect Manual Guardian Programmer's Guide TACL Reference Manual Open System Services User's Guide Code Profiling Utilities Manual These documents are available in the NonStop Technical Library at: Publishing history Part Number Product Version Publication Date NSDEE 4.0 October NSDEE 5.0 February R NSDEE 5.0 November NSDEE 6.0 June NSDEE 7.0 August 2017 Related documents 7

8 Introduction Introducing the debugging features for the HPE NonStop Development Environment for Eclipse The debugging features for the HPE NonStop Development Environment Version 7.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 7.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 For information about the supported versions of NSDEE and Native Inspect, see Supported release version updates (RVUs) on page 6. The NonStop Development Environment for Eclipse 7.0 Debugging Supplement and the NonStop Development Environment for Eclipse 7.0 User Guide are available online from the NonStop Technical Library at: Under User guide, scroll down to NonStop Development Environment for Eclipse 7.0 Debugging Supplement and NonStop Development Environment for Eclipse 7.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 7.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: 8 Introduction

9 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 7.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 7.0 User Guide and Debugging optimized code on page 9. More Information Preparing to launch a NonStop Application for debugging on page 10 Attaching the debugger to a NonStop process on page 17 Specifying program-initiated launch preferences on page 11 Debugging a Snapshot file on page 18 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: Sample variables view for optimized application on page 10, 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 Debugging tasks 9

10 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 on page 38. To create a new NonStop Application debug configuration, see Creating a new NonStop Application debug configuration on page Preparing to launch a NonStop Application for debugging

11 To modify an existing NonStop Application debug configuration, see Modifying an existing NonStop Application debug configuration on page 21. To specify options for the debugger, enter the information in the Debugger tab. See Specifying debugger options on page 43. 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. More Information Attaching the debugger to a NonStop process on page 17 Debugging a Snapshot file on page 18 Using the debug perspective for NonStop Applications on page 43 Debug configurations dialog for NonStop debugging configurations on page 63 Debug perspective for NonStop debugging configurations on page 62 Creating a new NonStop Application debug configuration on page 19 Modifying an existing NonStop Application debug configuration on page 21 Specifying program-initiated launch preferences NSDEE 7.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 also receives debug sessions launched by NSDEE. When using the program-initiated launch feature, 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: Program-initiated launch options on page 12. This option is a global setting that applies to all program-initiated launches handled by NSDEE. This option is checked by default. Specifying program-initiated launch preferences 11

12 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. Network connections To enable program-initiated debug launches, click Windows > Preferences > NonStop Development > Network Connections. Complete the system and user information. Check Accept incoming programinitiated debug connections. See Figure 3: Network connections on page Network connections

13 Figure 3: Network connections Optional: Use Network Connections screen to Switch user. For more information, see Switching user. 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. For more information, see Program-initiated launch options. 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. Launch configuration selection 13

14 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 Specifying Native Inspect settings Native Inspect (NI) settings affect the debug views. For more information about Debug views, see the C/C++ Development User Guide. You can configure NI settings for debug sessions using NI Settings preference page. Procedure 1. From the main toolbar, select Windows > Preferences > Run/Debug > Launching > NI Settings. The NI Settings screen is displayed. 14 Specifying Native Inspect settings

15 Figure 5: NI Settings 2. Specify the following NI Settings: a. Maximum number of complaints about incorrect symbols b. String Display Limit c. Threshold for repeated print elements d. Check or clear the following options: Display string value for char* variables Demangle C++ names in disassembly listings Demangle C++ names when displaying symbols Print 8-bit characters in strings as \nnn Show C++ static members Show unions interior to structures Show warnings for optimized code Stop at first null char when printing char array values Verbose messages For more information, see NI Settings parameters. 3. Click Apply. NI Settings parameters Maximum number of complaints about incorrect symbols Sets the maximum number of complaints about incorrect symbols. Default is 10. String Display Limit Sets the limit of string chars or array elements to print. The default value is 200 characters. A value of 0 means unlimited. NI Settings parameters 15

16 Threshold for repeated print elements Sets threshold for repeated print elements. The default value is 10. Display string value for char* variables Controls the display of char * variables. The default is on, and char * variables are automatically dereferenced for display. When you specify the off option, char * variables are not dereferenced for display. Demangle C++ names in disassembly listings Sets demangling of C++ names in disassembly listings. Demangle C++ names when displaying symbols Sets demangling of encoded C++ names when displaying symbols. Print 8-bit characters in strings as \nnn Sets printing of 8-bit characters in strings as \nnn. Show C++ static members Sets printing of C++ static members. Show unions interior to structures Sets printing of unions interior to structures. Show warnings for optimized code Sets a warning indicating that the debug information is incomplete for optimized code. The default is set to off. Stop at first null char when printing char array values Sets printing of char arrays to stop at first null char. Verbose messages Sets verbosity (information about progress is displayed as the command executes). Switching user Procedure If switch user is enabled, the debug and run sessions use only the switched user and not the logon user. You can use switch user for the following tasks: Program initiated debugging. Debugging configurations for NonStop application, NonStop attach process, and NonStop TS/MP server. Running configurations for NonStop application and NonStop TS/MP server. Configuring connection. 1. Navigate to the Network Connections screen. For more information, see Network connections. 2. Select the System from the drop-down menu. To add a system, click Add/Remove. 3. Select the Preferred Protocol. 4. Enter the user name to which you want to switch in Switch user. If the user name and the switch user name are the same, an error message is displayed: 16 Switching user

17 Switch user name must not be same as Remote NonStop System user. 5. Click Connect. The Switch User Authentication window appears. The switch user password is not validated while connecting the debugger. The validation is performed during the run or debug sessions. 6. Enter the password and click Ok. 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 on page 38. To create a new NonStop Attach Process debug configuration, see Creating a new NonStop Attach Process debug configuration on page 25. To modify an existing NonStop Attach Process debug configuration, see Modifying an existing NonStop Attach Process debug configuration on page 28. To specify options for the debugger, enter the information in the Debugger tab. See Specifying debugger options on page 43. 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. More Information Specifying debugger options on page 43 Ending a debugging session on page 60 Using the debug perspective for NonStop Applications on page 43 Debug configurations dialog for NonStop debugging configurations on page 63 Debug perspective for NonStop debugging configurations on page 62 Creating a new NonStop Attach Process debug configuration on page 25 Modifying an existing NonStop Attach Process debug configuration on page 28 Detaching the debugger from a NonStop process To detach the debugger from a process without terminating the process, use one of these methods: Attaching the debugger to a NonStop process 17

18 In the Debug view, click (Disconnect). From the main toolbar, select Run > Disconnect More Information Attaching the debugger to a NonStop process on page 17 Ending a debugging session on page 60 Debug perspective for NonStop debugging configurations on page 62 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 on page 38. To create a new NonStop Snapshot debug configuration, see Creating a NonStop Snapshot debug configuration on page 29. To modify an existing NonStop Snapshot debug configuration, see Modifying an existing NonStop Snapshot debug configuration on page 31. 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. More Information Specifying debugger options on page 43 Using the debug perspective for NonStop Applications on page 43 Debug perspective for NonStop debugging configurations on page 62 Debug configurations dialog for NonStop debugging configurations on page 63 Creating a NonStop Snapshot debug configuration on page 29 Modifying an existing NonStop Snapshot debug configuration on page 31 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 on page 19 NonStop Attach Process debug configurations on page Debugging a Snapshot file

19 NonStop Snapshot debug configurations on page 29 NonStop TS/MP Server configurations on page 32 In addition, Tasks common to all debug configurations on page 38 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 programinitiated launch preferences on page 11. Procedure 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. It also shows the names of debug configurations already created in this workspace. Figure 6: Debug configurations dialog box with Main tab for NonStop Application debug configurations 2. In the list left side of the Debug Configurations dialog, double-click the NonStop Application configuration type. A new debug configuration appears following 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 NonStop Application debug configurations 19

20 Debug Configurations dialog (see Figure 6: Debug configurations dialog box with Main tab for NonStop Application debug configurations on page 19) to edit your new configuration. When you finish entering the information for each tab, click Apply to apply your changes. To revert to the settings in effect the last time changes were applied, click Revert. 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 a 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 on page 68. 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 7.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. 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. 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 on page 23. If this is an OSS launch type, see Specifying environment variables for OSS launch types on page Optional: If you want to specify options for the debugger to use, enter the information in the Debugger tab. See Specifying debugger options on page Optional: Specify the memory debugger options in the Memory tab. For information about this tab, see Specifying memory debugging options. 9. Optional: By default, the debugger searches for source files at the path recorded when the application was compiled. 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 on page Debugging tasks

21 10. 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 on page 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 Procedure To modify an existing NonStop Application debug configuration: 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. 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 on page 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. 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 on page 19. 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 on page 22. 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: I. If this is a Guardian launch type, see Specifying DEFINEs, ASSIGNs, and PARAMs for Guardian launch types on page 23. II. If this is an OSS launch type, see Specifying environment variables for OSS launch types on page 24. d. If you want to specify options for the debugger to use, enter the information in the Debugger tab. See Specifying debugger options on page 43. e. Optional: Specify the memory debugger options in the Memory tab. For information about this tab, see Specifying memory debugging options. f. 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 Modifying an existing NonStop Application debug configuration 21

22 specified, either the default or alternate locations. See Specifying alternate source file locations on page 39. g. 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 on page 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. More Information Creating or modifying debug configurations on page 18 Debug configurations dialog for NonStop debugging configurations on page 63 Specifying arguments for NonStop Application debug configurations You can use the Arguments tab to specify the following: The options used by the run command when a program is launched. The arguments to pass to the application. A working directory other than your home directory. The following figure shows the Arguments tab for NonStop Application debug configurations. Procedure 1. To specify arguments for the run command used to launch the application under debugger control, enter them in the box after 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/ 22 Specifying arguments for NonStop Application debug configurations

23 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 after 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: a. For OSS launch types, select Set working directory. For Guardian launch types, select Set initial $volume.subvolume. b. 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. To apply your changes, click Apply. 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. 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: Environment tab for NonStop Application debug configurations, Guardian launch type on page 24) 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. Specifying DEFINEs, ASSIGNs, and PARAMs for Guardian launch types 23

24 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 Specifying environment variables for OSS launch types You can specify OSS environment variables for OSS launch types using the Environment tab 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. The following figure shows the Environment tab for NonStop Application debug configurations, OSS launch type. 24 Specifying environment variables for OSS launch types

25 NonStop Attach Process debug configurations Creating a new NonStop Attach Process debug configuration Procedure 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. It also shows 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 under 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 to edit your new configuration. When you finish entering the information for each tab, click Apply to apply your changes. Or, click 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 a NonStop Attach Process debug configuration. However, that debug configuration must already have the correct launch type. NonStop Attach Process debug configurations 25

26 Figure 8: Debug Configurations dialog for NonStop Attach Process debug configuration 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 on page 68. 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 7.0 User Guide d. Select one of the following NonStop Process options: CPU, PIN By default, this option is selected. Name ($XYZ) This option is disabled for OSS launch types. OSS Pid 26 Debugging tasks

27 This option is disabled for Guardian launch types. e. Specify the NonStop Process you want to debug in the corresponding box. Enter the process details in the following format: CPU, PIN - For example, 1,234. Name - For example, $XYZ. OSS Pid - For example Enter the process details in the corresponding box in the correct format. If the details are not entered or are in an incorrect format, an error message is displayed and the Debug option is disabled. If you click Browse: I. If you selected the Guardian NonStop launch type, the version of the Process Browser dialog in Figure 9: Process browser dialog for Guardian launch types on page 27 appears. In this example, $ZHOME is entered in the process filter, so only rows that contain the text ZHOME are displayed: II. Figure 9: Process browser dialog for Guardian launch types If you selected the OSS NonStop launch type, the version of the Process Browser dialog in Figure 10: Process browser dialog for OSS launch types on page 28 appears: Debugging tasks 27

28 Figure 10: Process browser dialog for OSS launch types 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 on page Optional. By default, the debugger searches for source files at the path recorded when the application was compiled. 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 on page Optional: Specify the memory debugger options in the Memory tab. For information about this tab, see Specifying memory debugging options. 8. 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 on page To apply your changes, click Apply. To revert to the settings in effect the last time changes were applied, click Revert. Modifying an existing NonStop Attach Process debug configuration Procedure To modify an existing NonStop Attach Process debug configuration: 1. From the main toolbar, select Run > Debug configurations. 28 Modifying an existing NonStop Attach Process debug configuration

29 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 and 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 many debug configurations, find the one you want to select by filtering the results as described in Listing and filtering debug configurations on page If you want to change the name of this configuration, enter the new name in the Name box. 4. Modify the setting options are required 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 name, and the NonStop process details. 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 on page 25. b. If you want to specify options for the debugger, enter the information in the Debugger tab. See Specifying debugger options on page 43. c. Optional: Specify the memory debugger options in the Memory tab. For information about this tab, see Specifying memory debugging options. d. By default, the debugger searches for source files at the path recorded when the application was compiled. 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 on page 39. e. 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 on page 79. f. 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. More Information Creating or modifying debug configurations on page 18 Debug configurations dialog for NonStop debugging configurations on page 63 NonStop Snapshot debug configurations NonStop Snapshot debug configurations dialog box is used to perform the following actions: Creating a NonStop Snapshot debug configuration on page 29 Modifying an existing NonStop Snapshot debug configuration on page 31 Creating a NonStop Snapshot debug configuration Procedure 1. From the main toolbar, select Run > Debug configurations. NonStop Snapshot debug configurations 29

30 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 and 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 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 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. To specify the NonStop launch type, select Guardian or OSS. Your selection determines what types of remote paths are allowed in all the tabs of the Debug Configuration dialog and all 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 on page 68 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 7.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. To apply your changes, click Apply. To revert to the settings in effect the last time changes were applied, click Revert. 30 Debugging tasks

31 Figure 11: 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 on page 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 on page 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 on page To apply your changes, click Apply. To revert to the settings in effect the last time changes were applied, click Revert. Modifying an existing NonStop Snapshot debug configuration Procedure To modify an existing NonStop Snapshot debug configuration: 1. From the main toolbar, select Run > Debug configurations. The Debug Configurations dialog appears. 2. In the Debug Configurations dialog, in the configurations list, select the debug configuration you want to modify. Modifying an existing NonStop Snapshot debug configuration 31

32 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 on page 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 (Figure 11: Main tab for NonStop Snapshot debug configurations on page 31), 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 on page 29. b. If you want to specify options for the debugger, enter the information in the Debugger tab. See Specifying debugger options on page 43. 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 on page 39. 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 on page Click Apply to apply your changes. To revert to the settings in effect the last time changes were applied, click Revert. More Information Creating or modifying debug configurations on page 18 Debug configurations dialog for NonStop debugging configurations on page 63 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 on page 32 Modifying an existing NonStop TS/MP Server debug configuration on page 36 TS/MP Debug configurations are used to debug the server class from the server class startup. To debug an existing or running TSMP server class, use NonStop Attach Process debug configurations, which will not alter or delete the configuration. Once the debugging session is completed or terminated, NSDEE deletes the server class configuration. Creating NonStop TS/MP Server debug configuration Procedure 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. 32 NonStop TS/MP Server configurations

33 A new debug configuration appears below the 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 Source Common For more information on Debug Configuration tabs, see Debug configuration group box on page 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 12: 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 on page 68. This field 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 7.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. Debugging tasks 33

34 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. 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 13: 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: I. Enter the name of the server class in the Name box. II. To specify the status of the server class, select New or Restart option. If you select Restart option, Delete the server class, if exist. option and Server Attributes fields are disabled. III. 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. d. Select Configure parameters from Add Commands option. 34 Debugging tasks

35 I. Click Add Commands. The Add Server Commands window is displayed. II. When the debug session is launched, NSDEE configures the server class settings with the following values, MAXSERVERS with 1, DEBUG with ON, and other user specified server class attributes and starts the server class. Once the debugging session is completed or terminated, NSDEE deletes the server class configuration. Select the check box corresponding to the desired server attributes. NOTE: The CPUS and MAXSERVERS settings are disabled in Add Server Commands window. III. 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 on page 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 on page 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 on page 43. Debugging tasks 35

36 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 on page Optional: In the Common tab, set other options related to the Eclipse workspace. For more information, see Common tab for NonStop debug configurations on page 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 Procedure 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 on page 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 Modifying existing NonStop TS/MP Server debug configuration. 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. 36 Modifying an existing NonStop TS/MP Server debug configuration

37 Table 1: Modifying existing NonStop TS/MP Server debug configuration Tabs in Debug Configurations dialog box Main TS/MP Server Arguments Environment Debugger 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. 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 on page 32. 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 on page 70. 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 on page 71. To modify the options for the debugger to use, change the information in the Debugger tab. For more information, see Specifying debugger options on page 43. Table Continued Debugging tasks 37

38 Tabs in Debug Configurations dialog box Source Common Procedure 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 on page 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 More Information Creating or modifying debug configurations on page 18 Configurations list on page 64 Listing and filtering debug configurations To filter the list of debug configurations shown in the configuration list in the Debug Configurations dialog, 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. Deleting an existing debug configuration To delete an existing debug configuration shown in the configuration list in the Debug Configurations dialog, use either of these methods: Click the debug configuration to select it, then click (Delete). Right-click the debug configuration and select Delete. More Information Listing and filtering debug configurations on page 38 Configurations list on page 64 Specifying memory options Procedure 1. While creating or modifying debugging configurations, navigate to the Memory tab in the Debugging Configuration dialog. 38 Tasks common to all debug configurations

39 For more information, see steps 1 and 2 in Creating a new NonStop Application debug configuration. Figure 14: Memory tab 2. Set the following options as required: Enable dynamic memory debugging settings Once you select this option, the other options are enabled. Use rtcdll at the following path Set Max depth of stack frames to report Enable heap profiling Minimum heap size allocated Enable leak profiling Minimum leak size bytes Monitoring string corruption Enable bounds-checking Enable detection of double-frees and frees Set heap block size Set program heap size For more information, see Memory tab. 3. Click Apply. 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 to direct the debugger to search in alternate locations. Specifying alternate source file locations 39

40 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. The following figure shows the 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 12: Debug Configurations dialog for NonStop TS/MP Server on page 33 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. To add or remove entries from the list, use the Add and Remove buttons to the right of the list. To edit existing entries, select Edit. To restore the default setting of a single default rule, select Restore Default. 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 the ones 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. 40 Debugging tasks

41 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. The remote compile-time location. 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 Remote Compile-Time File Path (This is the default rule for remote NonStop projects and applications built on NonStop servers outside of NSDEE.) 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 on page 77. 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 on page 42. The rule you selected is added to the list of source lookup path entries shown in the Source tab. Table Continued Debugging tasks 41

42 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 on page 77. 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 on page 42. Procedure 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 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. More Information Creating or modifying debug configurations on page 18 Source tab on page Debugging tasks

43 Specifying debugger options You specify debugger options for a debug configuration using the Debugger tab (Figure 15: Debugger tab on page 43). Figure 15: 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. More Information Creating or modifying debug configurations on page 18 Debugger tab on page 72 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 on page 62. Specifying debugger options 43

44 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 16: 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 on page 44 Controlling the execution of a NonStop Application on page 45 NonStop Signals on page 59 Setting watchpoints on page 45 Setting watch expressions on page 45 Setting breakpoints on page 47 Inspecting and modifying variable values on page 47 Inspecting and modifying register values on page 48 Inspecting and modifying memory on page 52 Debugging NonStop applications using Native Inspect (einspect/xinspect) commands on page 60 Ending a debugging session on page 60 Inspecting the stack 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 44 Inspecting the stack

45 about this task, see the C/C++ Development User Guide. (Available from the Eclipse Workbench help menu. Select Help > Help Contents.) More Information Debugging a Snapshot file on page 18 Debug perspective for NonStop debugging configurations on page 62 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. More Information Debugging a Snapshot file on page 18 Debug perspective for NonStop debugging configurations on page 62 Setting watchpoints 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 on page 60. For more information about the mab command, see the Native Inspect Manual. More Information Entering Native Inspect commands from the console view on page 60 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.) Controlling the execution of a NonStop Application 45

46 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 Procedure 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 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. More Information Debug perspective for NonStop debugging configurations on page 62 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. 46 Casting watch expressions to NonStop data types

47 Setting breakpoints 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. More Information Debug perspective for NonStop debugging configurations on page 62 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 Procedure 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. Setting breakpoints 47

48 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. 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 Considerations 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 on page 9. 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. More Information Inspecting and modifying register values on page 48 Inspecting and modifying memory on page 52 Specifying debugger options on page 43 Debugging optimized code on page 9 Debug perspective for NonStop debugging configurations on page 62 Debugger tab on page 72 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. 48 Function return values

49 Figure 17: Registers view TNS/E Debugging tasks 49

50 Figure 18: 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 Procedure 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. 50 Adding a register group

51 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. More Information Inspecting and modifying variable values on page 47 Inspecting and modifying memory on page 52 Specifying debugger options on page 43 Debug perspective for NonStop debugging configurations on page 62 Debugger tab on page 72 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. 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. Restoring default register groups 51

52 Figure 19: Segments view NOTE: The details pane displays only Selection attribute if SPR T1237H01^ABG or earlier versions of the debugger are used. More Information Specifying debugger options on page 43 Debug perspective for NonStop debugging configurations on page 62 Debugger tab on page 72 Inspecting and modifying memory 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.) More Information Inspecting and modifying register values on page 48 Debug perspective for NonStop debugging configurations on page 62 Debugger tab on page 72 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. 52 Inspecting and modifying memory

53 Figure 20: Modules view In Modules view, right-click on the required entry and select one of the following from the context menu: To load the symbol files for all load modules without a loaded symbol file, select Load Symbols For All. Or, using the Modules view toolbar, click. For more information, see section Loading symbol files for all modules. To search for an entry in the view, select Find. To load symbol information for the selected module, select Load Symbol File. For more information, see section Loading symbol file for a module on page 53. NOTE: If there are different symbol file paths for the load modules or you require immediate symbol table loading, use Load Symbol File option. To unload the symbol file associated with the selected module, select Unload Symbol File. If a symbol file is not loaded for the selected module, then the Unload Symbol File option is not displayed. To update the load modules displayed for the selected debug session and the attributes displayed in the details pane for the selected module, select Refresh. Loading symbol file for a module Procedure 1. In Modules view, right-click on the required entry and select Load Symbol File. Or, to load symbol files for all load modules without a loaded symbol file, select Load Symbols For All. The Load Symbols For All option is enabled only when one more entries are selected in the Modules view. 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. Loading symbol file for a module 53

54 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 /. 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. More Information Specifying debugger options on page 43 Debug perspective for NonStop debugging configurations on page 62 Debugger tab on page 72 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. Loading symbol files for all modules Procedure In Modules view, right-click on an entry and select Load Symbols For All. The Load Symbols For All option is enabled only when one or more entries are selected in the Modules view. 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 54 Loading symbol files for all modules

55 Show Columns Select Columns 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 21: FileOpens view 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. More Information Specifying debugger options on page 43 Debug perspective for NonStop debugging configurations on page 62 Debugger tab on page 72 Viewing heap profile report Prerequisites Procedure The Heap Profile view displays outstanding heap allocations at a specific breakpoint at runtime. Each row in the view represents heap allocation at a particular address in a function. It also shows the stack trace of a specific allocation. This information is used to analyze heap usage of an application and tune its memory requirements. To view heap profile reports, you must enable Heap profile settings in the Debug Configuration dialog. 1. Click Window > Show View > Other. The Other menu selection window is displayed. 2. Select Debug > Heap profile. The Heap profile view with the report is displayed. It shows the following columns: Viewing heap profile report 55

56 No Total bytes Blocks Address Function Example Figure 22: Heap profile For more information, see Heap profile report. If you have not selected any entry in the Heap profile view, the heap allocation usage summary is displayed in the details pane window when the target program is suspended. If you select a heap allocation entry, these details are cleared. To refresh the view with the heap data at a specific breakpoint: Right-click in the heap profile section, and in the context menu select Refresh. To view the stack trace of the selected heap allocation entry, select each row in the heap profile view. A sample heap allocation usage summary: Heap Usage Summary Actual Heap Usage: Heap Start = 0x Heap End = 0x0843d000 Heap Size = bytes Outstanding Allocations: bytes allocated in 1011 blocks A sample stack trace of the selected heap allocation entry: Stack trace of the selected entry bytes at 0x7bd63000 (9.86% of all bytes allocated) in h_func () at testc:108 in main () at testc:17 56 Debugging tasks

57 in _start () in $START$ () Viewing leak profile report The Leak profile view displays memory leaks in a debugging application. Prerequisites To view leak profile reports, enable Leak profile settings in the Debug Configuration dialog. Procedure 1. Click Window > Show View > Other. The Other menu selection window appears. 2. Select Debug > Leak profile. The Leak profile view with the report is displayed. It shows the following columns: No Total bytes Blocks Address Function For more information, see Leak profile report on page 81. Example Figure 23: Leak profile If you have not selected any entry in the Leak profile view, the memory leak summary is displayed in the details pane window at a specific breakpoint. If you select a leak entry, these details are cleared. To refresh the view with the leak data at a specific breakpoint: Right-click in the leak profile section, and in the context menu select Refresh. To view the details of a specific leak in the detail pane, select the required row or leak error. A sample memory leak summary: 2439 bytes leaked in 25 blocks A sample leak error: 245 bytes leaked in 8 blocks (10.05% of all bytes leaked) These range in size from 26 to 36 bytes and are allocated in strdup () in link_the_list () at testc:55 in main () at testc:13 in _MAIN () Viewing leak profile report 57

58 Viewing heap corruption report The Heap Corruption view displays the corruption profile of all heap allocations that are corrupted when the target program is suspended. These corruptions are caused by a string corruption or out of bound writes. Prerequisites To view heap corruption reports, enable the event monitoring options (Monitoring string corruption and Enable bounds-checking) in the Debug Configuration dialog. Procedure 1. Click Window > Show View > Other. The Other menu selection window is displayed. 2. Select Debug > Heap Corruption. The Heap Corruption view with the report is displayed. It shows the following columns: No Total bytes Blocks Corruption Address Function For more information, see Heap Corruption report. Example To view details of a specific heap corruption, click Show Details in the context menu in the heap corruption view. To refresh the view with the heap corruption at a specific breakpoint: Right-click in the heap corruption section, and in the context menu select Refresh. A sample heap corruption: 10 bytes at 0x08429d38 (33.33% of all bytes allocated) #0 sm_malloc() at \PELICAN.$DATA4.USER.EX5C:12 #1 main() at \PELICAN.$DATA4.USER.EX5C:21 #2 _MAIN() at \SPEEDY.$RLSE.T8432H02.CPLMAINC:46 58 Viewing heap corruption report

59 Heap events Heap events suspend the program execution and report the error in the Debugger Console. Heap event monitoring settings are enabled in the Memory tab of the Debug Configuration dialog. The event monitor setting options are: Set heap block size Set program heap size Enable detection of double-frees and frees For more information, see Memory tab. Viewing leak report Procedure The Leak Report view displays the leak error report after the application debugging is complete. 1. Click Window > Show View > Other. The Other menu selection window is displayed. 2. Select Debug > Leak Report. The Leak Report view is displayed. It shows the following columns: Description Resources Path Location NonStop Application For more information, see Leak report. 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 on page 59 Modifying NonStop Signals on page 59 Viewing NonStop Signals Procedure 1. Select Window > Show View > Other > Debug > NonStop Signals. 2. 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. Modifying NonStop Signals Procedure 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. Heap events 59

60 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 Debugger 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 on page 79. 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 Procedure You can enter Native Inspect commands that NSDEE supports from the Native Inspect (einspect or xinspect) console in the Debugger Console view: 1. 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. More Information Debug perspective for NonStop debugging configurations on page 62 Native Inspect commands supported by NSDEE on page 79 Enabling GDB traces From NSDEE 7.0 release onwards, the GDB traces console is not enabled by default. This console is hidden by default. You can enable the GDB traces console using the GDB preference screen. For information on enabling GDB trace console, see Debug preferences section in C/C++ Development User Guide. Ending a debugging session The debugging session ends when one of these conditions occurs: 60 Debugging NonStop applications using Native Inspect (einspect/xinspect) commands

61 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. More Information Using the debug perspective for NonStop Applications on page 43 Controlling the execution of a NonStop Application on page 45 Detaching the debugger from a NonStop process on page 17 Debugging tasks 61

62 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 16: Debug perspective for NonStop Applications on page 44 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 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 on page 63. The Debug Configurations dialog has features specific to the NonStop debug configurations. See Debug configurations dialog for NonStop debugging configurations on page 63. 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 24: Debug view for NonStop debugging on page 63). 62 Reference information

63 Figure 24: 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 The dialog Debug Configurations includes these components: Debug configurations dialog for NonStop debugging configurations 63