Controls where the Debugger looks for DSOs when you invoke the Debugger on an executable or core file. The Library Search Path dialog allows you to reset the LD_LIBRARY_PATH and _RLD_ROOT environment variables. You can also reset _RLD_LIST to control the set of DSOs that will be used by the program. See the rld(1) man page for more information on these variables. Any changes you make to these variables are propagated into Execution View when you run the program.

There are two ways to open this dialog. First, select Admin -> Library Search Path from the Main View window menu bar, or the Library Search Path dialog opens automatically if you invoke the Debugger on an executable or core file and it is unable to find all of the required DSOs. In this case, an annotated list of required DSOs displays at the top of the dialog box with such status messages as OK, Error: Cannot find library, or Error: Core file and library mismatch (which indicates that the Debugger found a DSO that did not match the core file). Below this list are three to nine fields in which you can modify the value of the corresponding named environment variable.

Opens a dialog that allows you to enter a new pathname.

Displays the Multiprocess View window, which allows you to control processes and threads. You should note that if you exit from Multiprocess View, you will exit from your debugging session. More additional information about Multiprocess View, refer to “Multiprocess View”.

Provides a toggle to turn on GLdebug. GLdebug is a graphical software tool for debugging application programs that use the IRIS Graphics Library (GL). GLdebug locates programming errors in executables when GL calls are used incorrectly.

Changes the current process or attaches to a process. You will be queried for the new process ID. You can select one from the list of items presented, type one in or paste one in from another window. Switching processes changes the session.

Changes the current executable or loads an executable. This option also allows you to debug a different core file.

Releases the process from the Debugger. This allows you to make changes to the source code. You must detach the process before you recompile the program.

Allows you to use the previously saved preference settings from a file you choose in the Load Settings dialog.

Allows you to save the current preference settings to an initialization file used when the Debugger is first started, or any file you choose through this dialog. These can include such items as window sizes, current views, window configurations, and so on.

Iconifies all session views.

Brings all session view windows to the foreground and displays any iconified windows.

Allows you to run other WorkShop tools. You can switch to the other tools by selecting Build Analyzer, Static Analyzer, Performance Analyzer, or Tester. Selecting Debugger allows you to start another debugging session. If you have ProDev ProMP (formerly called WorkShop Pro MPF) installed on your system, the Parallel Analyzer selection is also available.

Closes the Main View window.

Closes all views in the session and terminates the session.

Displays values from an array or array-slice in a two-dimensional spreadsheet and optionally in a three-dimensional representation; that is, a bar graph, surface, multiple lines, or points in space. These help you pick out bad data more readily. Arrays can contain up to 100 x 100 elements.

Displays the call stack along with parameters to the calls. If you double-click an entry in the stack, you switch the current context to that entry and you can check the state of variables.

Displays assembly code corresponding to the source code.

Displays an Ada-specific window used for exception handling.

Displays the iconified Execution View window, which handles the input and output of the target process.

Evaluates expressions in Fortran, C, or C++. To enter an expression, select it in the source code display and paste it into the Expression View field, using the middle mouse button.

Displays a list of source files and library routines used by the current executable. Double-click a source file in the list to load it directly into the source display area in Main View or Source View windows. The Search field allows you to find files in the list quickly.

Displays the value at a given memory address.

Monitors the resource usage of a running process without saving the data. (Used with the Performance Analyzer.)

Displays the values stored in the hardware registers for the target process.

Displays the signals that can occur. You can specify which signals trigger traps and which are to be ignored.

Displays source code. Allows you to set traps, perform searches, and inspect source code without losing information in the Main View window.

Displays data structures in a graphical format. You can de-reference pointers by double-clicking.

Allows you to set traps at the entry to or exit from system calls.

Brings up an Ada-specific view that provides task and callstack information for processes.

Allows you to set, edit, and manage traps. The Trap Manager is used by both the Debugger and the Performance Analyzer.

Displays values of local variables and parameters for the current context.

Provides you with specific debugging support for X/Motif applications. There are various examiners for different X/Motif objects, such as widgets and X graphics contexts, that might be difficult or impossible to inspect using ordinary Debugger functionality.

Loads a source file.

Provides you with a popup dialog that gives you a selection of recently-opened files from which to choose.

Records changes made during the debugging session to the source file. You must first select Make Editable, which appears in the Source menu when the file is read-only.

Records changes made during the debugging session to the source file under a different filename. You must first select Make Editable , which appears in the Source menu when the file is read-only.

Records the information in the display area as a text file.

Inserts the text of a file within your current file. You must first select Make Editable, which appears in the Source menu when the file is read-only. You must first select Make Editable, which appears in the Source menu when the file is read-only.

Starts your default editor on the current file. The default editor is determined by the editorCommand resource in the app-defaults file. The value of this resource defaults to wsh -c vi +%d, which means run vi in a wsh window and scroll to the current line. If the editor allows you to specify a starting line, enter %d in the resource to indicate the new line number.

Displays the Build View window, which allows you to compile the source code associated with the current executable.

Toggles the source code displayed between read-only and writable states so that you can edit your code.

Searches for a literal case-sensitive, literal case-insensitive, or regular expression. After you have set your target and clicked Apply (or pressed Enter), each instance is marked by a search target indicator in the scroll bar. You can search forward or backward in the file by clicking the Next and Prev buttons. You can also click an indicator with the middle mouse button to scroll to that point. Clicking Reset removes the search target indicators.

Allows you to scroll to a position in the source code by specifying a line number. Go To Line brings up a dialog box.

You can enter a line number or use the slider at the top of the box to select a line number. You do not have to display line numbers to use this feature.

Provides access to the configuration management tool, if you have designated one.

Type the following at the Execution View prompt:

/usr/sbin/cvconfig [rcs | sccs | ptools | clearcase]

---

Note: You must have root permissions to run cvconfig.

---

The Versioning submenu appears.

Selecting any submenu option displays a shell in which you can access the configuration management tool. The following selections are available on the submenu:

Displays or hides line numbers in the annotation column corresponding to the source code.

Allows you to choose the format type for the toolbar. The options are Text Only, Icons Only, or Icons and Text. Text Only was the only format for the toolbar prior to release 2.9. Icons Only and Icons and Text are options which display icon options for more visual debugging.

This menu item enables or disables the context sensitive pop-up help option. Some of the key menu items, buttons, and data entry areas have pop-up help statements attached to them to give the user hints on what to use them for or how to use them.

Displays the Annotations Preferences dialog box, which allows you to show or hide column annotations and menus specific to the different WorkShop tools. If you have purchased ProDev ProMP, you can display and manipulate loop indicators. The Performance toggle displays experiment statistics. The Tester module allows you to see coverage statistics. Turning off the Performance toggle deletes the performance annotations from the Source View .

Hides or displays the annotation column, which is located to the left of the source code display area.

Allows you to choose the task for your performance analysis. The choices available are shown in Figure A-3. You may select only one task per performance analysis run. If none of the given tasks satisfy your requirements, you can choose Custom, which brings up the configuration dialog open to the General tab. From here, you can design your own task requirements.

Figure A-3. Perf Menu and Subwindows

Launches the Performance Analyzer. For complete information about the Performance Analyzer, see the ProDev Workshop: Performance Analyzer User's Guide.

Brings up the configuration dialog open to the Runtime tab as shown in Figure A-3. The dialog opens with the Experiment Directory text field filled in with a default value. The Performance Analyzer provides a default directory named test0000. If you use the default or any other name that ends in four digits, the four digits are used as a counter and will be incremented automatically for each subsequent experiment.

Sets a breakpoint at a designated line in your source code. To set a breakpoint at a line displayed in the Main View or Source View windows:

The preferred method for setting a breakpoint is to click in the annotations area of the Main View window, across from the line at which you want to set the breakpoint.

Sets a breakpoint at the beginning of a function. To set a breakpoint at a function, click on the function name in the source code display area and select the Set Trap submenu, then choose the Stop At Function Entry option.

Sets a breakpoint at the end of a function. To set a breakpoint at a function exit, click on the function name in the source code display area and select the Set Trap submenu, then choose the Stop At Function Exit option.

Sets a sample trap at a line displayed in the Main View or Source View windows. To set a sample trap:

Sets a sample trap at the beginning of a function. To set the sample trap, highlight the function name in the source code display area, then pull down the Set Trap submenu and select the Sample At Function Entry option.

Sets a sample trap at the end of a function. To set the sample trap, highlight the function name in the source code display area, then pull down the Set Trap submenu and select the Sample At Function Exit option.

Designates the stop trap type.

Designates the sample trap type.

Interacts with Source View. If set to true, all subsequent Source View trap requests will be group traps. That is, all members of the process group will apply this trap. This option is the same as typing stop pgrp in filename from the command line. Default is false unless you are using IRIX 6.5 pthreads, when the implied setting is always true.

Interacts with Source View. If set to true, all subsequent Source View trap requests will apply the Stop All command to the trap. That is, whenever this trap is encountered, all other members of the process group also will be stopped. This option is the same as typing stop all in filename from the command line. Default is false unless you are using IRIX 6.5 pthreads, when the implied setting is always true.

Continues the process to the selected point in the program unless some other event interrupts. Select a line by clicking on it. The process must be stopped before you can use Continue To.

Goes directly to a selected point within the same function, jumping over intervening code. Then the Debugger waits for a command to resume execution. Select a line by clicking on it.

Allows you to edit text using the Debugger editor.

Allows you to edit text by using an external editor. The default editor is vi, but can be changed by using the Set Edit Tool pop-up menu in the Admin menu of the Status window. See “Fix+Continue Status Window”, for further information.

Compiles your modified program and loads it for execution. You can execute the modified program by clicking on the Run or Continue buttons in the Main View window.

Allows you to see the difference between the original code and your modifications. See “Show Difference Submenu”, for further information.

Enables or disables your changes. This switch allows you to see how your application executed before and after the changes you made.

Allows you to save your changes to a file. You can save changes to the current source file (the default) or to a separate file.

Launches the Save File+Fixes As dialog that allows you to update the current session and save all the modifications.

Allows you to change to different views. Fix+Continue supports status, message, and build environment windows. See “View Submenu”, for further information.

Allows you to set your Fix+Continue preferences. See “Preferences Submenu”, for further information.

Takes you out of edit mode and cancels any changes you have made.

Deletes any modifications that you made.

Provides information on the selected window or menu.

Provides general information on the current tool.

Displays the entire list of help topics, alphabetically, hierarchically, or graphically.

Lists the keys and shortcuts for the current tool.

Provides copyright and version number information on the tool.

Launches the Open dialog that allows you to choose a file to load into Source View.

Records changes made to the file during the current debugging session. You must first select Make Editable from this File menu when the file is read only.

Records changes made during the debugging session to the source file under a different file name, the name of which you can enter or select using the Save As Text dialog.

Records information in the display area as a text file, the name of which you can enter or select using the Save As Text dialog.

Launches the Open Separate dialog that allows you to create a new Source View with the contents of a different source file.

Inserts the text of a file within your current file. This item description is available only if the file is editable. The Make Editable item description from this File menu can be used to switch the file from read only.

Clones the current window.

Starts your default editor on the current file. The default editor is determined by the editorCommand resource in the app-defaults file. The value of this resource defaults to wsh -c vi +%d, which means run vi in a wsh window and scroll to the current line. If the editor allows you to specify a starting line, enter %d in the resource to indicate the new line number.

Displays the Build View window that allows you to compile the source code associated with the current executable.

Toggles the source code displayed between (Read Only) and (Editable) so that you can edit your code.

Searches for a literal case-sensitive, literal case-insensitive, or regular expression. After you have set your target and clicked Apply (or pressed Enter), each instance is marked by a search target indicator in the scroll bar. You can search forward or backward in the file by clicking the Next or the Prev button. You can also click an indicator with the middle mouse button to scroll to that point. Clicking Reset removes the search target indicators.

Launches the Go To Line dialog that allows you to go to a specific line in the source. You can type in the line, or select the line number via the slider bar.

Provides access to the configuration management tool, if you have designated one.

The cvconfig script allows you to designate ClearCase, RCS or SCCS. Type the following:

/usr/sbin/cvconfig [rcs | sccs | ptools |  clearcase]

You must have root permissions to run cvconfig .

Selecting any option displays a shell in which you can access the configuration management tool. The selections in the submenu are:

Contains the following options:

Dismisses the Source View window.

Opens a dialog that allows you to switch the process or thread currently focused on in the Main View window to the process or thread selected in the Multiprocess View window. Selecting a call stack entry changes the Main View window's focus to that process or thread and positions the cvmain window at the offset of the selected call stack.

Brings up a new Main View window for the selected process or thread.

Opens a dialog box that allows you to enter the name of a thread on which focus should be switched. This is useful when multiple threads, all at the same location, are collapsed into a single line. While Change focus to this entry always takes you to the first thread, Goto allows you to jump to any thread.

Opens a dialog in which you can select from a list of process ids. Selecting a process id (PID) in the dialog and pressing OK will cause the process to be attached and added into the Multiprocess View window's list of processes.

After you select a process/thread (by highlighting it), click on Remove to remove it from the list of processes in the Multiprocess View window. A process in a sproc share group cannot be removed from the process group.

Activates the current window in a set of cloned windows.

Creates a clone of the current window.

Launches the Save Text dialog. This dialog allows you to save your current session as text in a file you designate.

Closes the current window.

Opens the Load User Defined Exceptions dialog that allows you to add additional exceptions to the predefined Ada exceptions.

Opens the Save User Defined Exceptions dialog that allows you to save any user-defined exceptions to the predefined Ada exceptions.

Deletes all exception traps.

Clears all exception traps. Clearing traps is not the same as deleting traps. Clearing only temporarily affects traps while deleting removes them permanently.

Resets all button actions.

Stops any time the exception is raised.

Stops when caught by a when others handler rather than an explicit handler or when unhandled.

Stops when the exception is unhandled.

Widget callback installed by XtAddCallback. Parameters include callback name and client_data XtPointer value. See “Callback Breakpoints Examiner”, for more information.

Widget event handler installed by XtAddEventHandler . Parameters include X event type and client_data XtPointer value. See “Event-Handler Breakpoints Examiner”, for more information.

Resource change caused by XtSetValues or XtVaSetValues. Parameters include resource name and resource value, both strings. See “Resource-Change Breakpoints Examiner”, for more information.

Timeout callback installed by XtAppAddTimeOut. Parameters include client_data XtPointer value. See “Timeout-Procedure Breakpoints Examiner”, for more information.

Input callback installed by XtAppAddInput. Parameters include client_data XtPointer value. See “Input-Handler Breakpoints Examiner”, for more information.

Various widget state changes (for example, managed or realized). Parameters include widget state. See “State-Change Breakpoints Examiner”, for more information.

X event received by target application. Parameters include X event type. See “X-Event Breakpoints Examiner”, for more information.

X request received by target application. Parameters include X request type. See “X-Request Breakpoints Examiner”, for more information.

Allows you to turn the tracing on and off.

Allows you to select the file name for the trace. If no file is selected, a default filename for the trace is chosen.

Allows you to perform an incremental, textural search for the trace list.

Launches a dialog that allows you to select the trace entry types you want displayed in the list.

Erases the trace file. Any subsequent trace information goes to the beginning of the file.

Allows you to choose a widget to examine by entering the widget address.

Allows you to choose a widget to examine by entering the widget name.

Allows you to move the parent of the currently selected widget.

Moves you to the previously selected widget.

Shows you the widget's children. (It is grayed out if the selected widget does not have children.)

Allows you to select the widget in the target process.

Click on this indicator to bring up a submenu from which you can select a different percentage.

Decreases the zoom percentage.

Increases the zoom percentage.

Shows the entire tree structure in another window along with an indication of which portion of the tree is currently being displayed in the full-sized Tree Examiner window.

This button shows/hides multiple connections between nodes on the graph. For example, if main calls foo several times, you will see a line (arc) for all calls made.

This button resets the graph back to its original configuration (before you began working with it). Also, hidden nodes will reappear.

Change the format of the window from up-down to left-right, or vice-versa.

Search for text in the tree using a Widget Hierarchy Search Text window.

Click on this indicator to change the kind of information being displayed in the nodes of the tree. This will bring up a submenu which allows you to choose Name, Class, ID (widget address) or Window (indicate <gadget> or address).

Contains a description of the trap.

Contains the condition of the trap.

Displays the current cycle count.

Displays the current trap count.

Allows you to toggle between display of full and partial path names.

Allows you to change the selected breakpoint's settings.

Allows you to add a new breakpoint.

Clears all the current breakpoint selections and text fields.

Deletes the selected breakpoint.

If selected with a check mark, the trap is enabled.

Contains a description of each trap, and a toggle to indicate whether or not the trap is active.

Allows you to perform an incremental textual search for the trap list.

Brings up the File dialog allowing you to load the traps from a file.

Brings up the File dialog allowing you to save the current traps to a file.

Highlight a line in the Main View window's source pane before selecting this option to set a breakpoint at the selected line.

Highlight a function name in the Main View window's source pane before selecting this option to set a breakpoint at the entry to the function.

Highlight a function name in the Main View window's source pane before selection this option to set a breakpoint at the exit from the function.

Causes a trap created to be a “stop” trap. Toggles with the Sample Trap Default.

Causes a trap created to be a “sample” trap. Toggles with the Stop Trap Default.

ON/OFF toggle to cause a trap created to have the “pgrp” option.

ON/OFF toggle to cause a trap created to have the All option.

Deletes all traps from the trap list.

Allows you to enter the name of the array variable. This entry is language-dependent.

For Fortran, the expression may be an array or a dummy array variable name. If the last dimension of the array is unspecified (*), a subscript value of 1 is assumed initially.

For C and C++, the entry may be an array or a pointer. If pointers are used, the expression is treated as though it were a single element, in which case you need to use the subscript controls to see more than the first element.

The expression used to view an element in the array. It is filled in automatically when you specify an array to view.

The expression supplied is language-specific. It represents the indexing expression used in the language to access a particular element. The subscripts are specified by special indexing variables ($i, $j, $k, and so forth) that can be manipulated in the subscript controls area.

Controls whether an index variable represents rows or columns (or neither) in the spreadsheet area. You are not limited by the number of dimensions of an array, but you can only view a two-dimensional orthogonal slice of the array at a time.

Indicates to which subscript the controls in the row refer.

Shows the value of the subscript for the element currently in the focus cell. You can enter a different value if you wish.

Lets you move the focus cell along the particular dimension.

Identifies the beginning visible element in that particular dimension.

Identifies the last visible element in that particular dimension. If you have an unspecified array, you can use this field to specify the last element in the vector to be displayed in the spreadsheet.

Specifies the increment between adjacent elements in the dimension to be displayed. A value of 1 displays consecutive data. Specifying some n greater than 1 allows you to display every n element in a vector.

Allows you to expose hidden portions of the subscript control area if your window is not large enough for viewing all of the controls.

Provides options for saving and reusing type-specific formats and expressions. You can also set preferences regarding how objects of a given type are to be displayed.

Provides display options for all objects in the display area.

Provides options for selected objects in the display area only.

Allows you to change or reformat a specific value in the result column. To access this pop-up menu, hold down the right mouse button while the cursor is over the result column.

Clears all the parsing errors and warnings.

Puts a check mark on the next unchecked error warning entry in the parse messages. It displays the corresponding file and line in the Source view, highlighting it according to the type of error or warning. The Next option does not work after all the entries in the messages are ticked.

Erases all the ticks, so that you can rescan all the error warnings from the beginning.

Sets the build environment to default that is displayed in the window.

Sets the build environment to that of the file that contains the currently selected function. You can change the file by clicking the Select File button, which launches the File dialog.

Launches the File dialog and allows you to select a file from which to set the build environment.

Clears the window.

Sets the build environment to what is displayed in the window.

Unsets the build environment.

Dismisses the window.

(For C and C++ only, when compiled with -o32.) Prompts you to add source code lines (for example, add_source "fmain.c":15.2 ). line_number must be within the body of a function. Entering a period (.) specifies the end of your input. The source lines you provide are added after the specified line. This command returns an ID existing or new, depending on whether the function affected has already been changed or not. The resulting new definition of the function is executed on its entry next time. See also delete_source and replace_source.

Lists all aliases without arguments. With arguments, it assigns command to shortform.

Assigns expression2 to expression1.

Attaches to specified process ID (pid).

Executes the specified function with any arguments supplied.

With no arguments, lists signals to be trapped. If a signal is specified, it's added to the list. If all is specified, it traps all signals.

Cancels pending function calls.

Continues execution from the current line to the entry to the specified function.

Continues execution from the current line until the specified line, if there is not an intervening breakpoint to stop execution.

Continues executing a program, or all processes, after a breakpoint. You can use both c and cont as aliases for continue.

Sends specified signal and continues executing a program after a breakpoint.

With no arguments, reports whether data referencing commands reference a core file. If so, displays the current core file. With filename provided, specifies core file to be debugged.

Deletes all traps. The all option deletes all breakpoints.

(For C and C++ only when compiled with -o32.) Deletes changes corresponding to the selected functions (for example, delete_changes getNumbers -file fmain.c). Once IDs are deleted, you will not be able to use the IDs again because the IDs associated with the selected functions are released. The default is -all. See also save_changes.

(For C and C++ only, when compiled with -o32.) Deletes the given line(s) if line_number or ,line_number (range) is within the body of a function. An example is:

delete_source "fmain.c":8.6,8.7

Deletes the specified breakpoint numbered trap_number , as obtained from the list generated when the status command is issued.

Detaches from the current process.

Deactivates all traps.

(For C and C++ only, when compiled with -o32.) Disables specified changes for selected functions (for example, disable_changes getNumbers -file fmain.c. Nothing happens if the selected function is already disabled. The compiled definition of the function is executed on its next entry. You can invoke this command when the process is stopped or on a running process when a function entry breakpoint is set.

Deactivates the specified breakpoint numbered trap_number, as obtained from the list generated when the status command is issued.

With expression, adds expression to the list of expressions displayed whenever the process stops. With no arguments, lists all expressions. See undisplay to delete an expression.

Moves down the specified number of frames in the call stack. down moves away from the direction of the caller.

Prints local variable values.

Reactivates all inactive traps.

(For C and C++ only when compiled with -o32.) Enables specified changes for selected functions (for example, enable_changes getNumbers -file fmain.c). Nothing happens if the selected function is already enabled. The latest accepted definition of the function is redefined on its next entry. You can invoke this command when the process is stopped or on a running process when a function entry breakpoint is set.

Reactivates the specified breakpoint numbered trap_number, as obtained from the list generated when the status command is issued.

Prints the contents of the memory address specified by expression, according to the specified format. count represents the number of formatted items. The following format options are available:

Displays the name of the current or specified file ( filename). If a file is specified, it becomes the current file.

Moves to the source code corresponding to the specified frame in the call stack or to the function in the executable if not on the stack.