Developer for System z, Version 7.6
Debugging your programs in full-screen mode
Using full-screen mode: overview
Debug Tool session panel
Session panel header
Source window
Monitor window
Log window
Memory window
Creating a preferences file
Displaying the source
Changing which file appears in the Source window
Entering commands on the session panel
Order in which Debug Tool accepts commands from the session panel
Using the session panel command line
Issuing system commands
Entering prefix commands on specific lines or statements
Entering multiple commands in the Memory window
Using commands that are sensitive to the cursor position
Using Program Function (PF) keys to enter commands
Initial PF key settings
Retrieving previous commands
Composing commands from lines in the Log and Source windows
Navigating through Debug Tool windows
Moving the cursor between windows
Switching between the Memory window and Log window
Scrolling through the physical windows
Enlarging a physical window
Scrolling to a particular line number
Finding a string in a window
How does Debug Tool search for strings?
Syntax of a search string
Finding the same string in a different window
Finding a string in the Monitor value area when SET MONITOR WRAP OFF is in effect
Finding the same string in a different direction
Specifying the boundaries of a search in the Source window
Example: Complex searches
Example: Searching for COBOL paragraph names
Displaying the line at which execution halted
Navigating through the Memory window
Displaying the Memory window
Navigating through the Memory window using the history area
Specifying a new base address
Creating a commands file
Recording your debug session in a log file
Creating the log file
Recording how many times each source line runs
Recording the breakpoints encountered
Setting breakpoints to halt your program at a line
Setting breakpoints in a load module that is not loaded or in a program that is not active
Controlling how Debug Tool handles warnings about invalid data in comparisons
Stepping through or running your program
Recording and replaying statements
Recording the statements that you run
Preparing to replay the statements that you recorded
Replaying the statements that you recorded
Changing the direction that statements are replayed
Stop the replaying
Stop the recording
Restrictions on recording and replaying statements
Restrictions on accessing COBOL data
Saving and restoring settings, breakpoints, and monitor specifications
Saving and restoring automatically
Disabling the automatic saving and restoring of breakpoints, monitors, and settings
Restoring manually
Performance considerations in multi-enclave environments
Displaying and monitoring the value of a variable
One-time display of the value of variables
Adding variables to the Monitor window
Displaying the data type of a variable in the Monitor window
Replacing a variable in the Monitor window with another variable
Adding variables to the Monitor window automatically
Saving the information in the automonitor section to the log file
How Debug Tool automatically adds variables to the Monitor window
Example: How Debug Tool adds variables to the Monitor window automatically
How Debug Tool handles characters that cannot be displayed in their declared data type
Modifying characters that cannot be displayed in their declared data type
Formatting values in the Monitor window
Displaying values in hexadecimal format
Monitoring the value of variables in hexadecimal format
Modifying variables or storage by using a command
Modifying variables or storage by typing over an existing value
Restrictions for modifying variables in the Monitor window
Opening and closing the Monitor window
Displaying and modifying memory through the Memory window
Modifying memory through the hexadecimal data area
Managing file allocations
Displaying error numbers for messages in the Log window
Displaying a list of compile units known to Debug Tool
Requesting an attention interrupt during interactive sessions
Ending a full-screen debug session
Debugging a COBOL program in full-screen mode
Example: sample COBOL program for debugging
Halting when certain routines are called in COBOL
Identifying the statement where your COBOL program has stopped
Modifying the value of a COBOL variable
Halting on a COBOL line only if a condition is true
Debugging COBOL when only a few parts are compiled with TEST
Capturing COBOL I/O to the system console
Displaying raw storage in COBOL
Getting a COBOL routine traceback
Tracing the run-time path for COBOL code compiled with TEST
Generating a COBOL run-time paragraph trace
Finding unexpected storage overwrite errors in COBOL
Halting before calling an invalid program in COBOL
Debugging a non-Language Environment COBOL program in full-screen mode
Example: sample non-Language Environment COBOL program for debugging
Defining a compilation unit as non-Language Environment COBOL and loading debug information
Defining a compilation unit in a different load module as non-Language Environment COBOL
Halting when certain non-Language Environment COBOL programs are called
Identifying the statement where your non-Language Environment COBOL program has stopped
Displaying and modifying the value of non-Language Environment COBOL variables or storage
Halting on a line in non-Language Environment COBOL only if a condition is true
Debugging non-Language Environment COBOL when debug information is only available for a few parts
Getting a non-Language Environment COBOL program traceback
Finding unexpected storage overwrite errors in non-Language Environment COBOL
Debugging a PL/I program in full-screen mode
Example: sample PL/I program for debugging
Halting when certain PL/I functions are called
Identifying the statement where your PL/I program has stopped
Modifying the value of a PL/I variable
Halting on a PL/I line only if a condition is true
Debugging PL/I when only a few parts are compiled with TEST
Displaying raw storage in PL/I
Getting a PL/I function traceback
Tracing the run-time path for PL/I code compiled with TEST
Finding unexpected storage overwrite errors in PL/I
Halting before calling an undefined program in PL/I
Debugging a C program in full-screen mode
Example: sample C program for debugging
Halting when certain functions are called in C
Modifying the value of a C variable
Halting on a line in C only if a condition is true
Debugging C when only a few parts are compiled with TEST
Capturing C output to stdout
Capturing C input to stdin
Calling a C function from Debug Tool
Displaying raw storage in C
Debugging a C DLL
Getting a function traceback in C
Tracing the run-time path for C code compiled with TEST
Finding unexpected storage overwrite errors in C
Finding uninitialized storage errors in C
Halting before calling a NULL C function
Debugging a C++ program in full-screen mode
Example: sample C++ program for debugging
Halting when certain functions are called in C++
Modifying the value of a C++ variable
Halting on a line in C++ only if a condition is true
Viewing and modifying data members of the this pointer in C++
Debugging C++ when only a few parts are compiled with TEST
Capturing C++ output to stdout
Capturing C++ input to stdin
Calling a C++ function from Debug Tool
Displaying raw storage in C++
Debugging a C++ DLL
Getting a function traceback in C++
Tracing the run-time path for C++ code compiled with TEST
Finding unexpected storage overwrite errors in C++
Finding uninitialized storage errors in C++
Halting before calling a NULL C++ function
Debugging an assembler program in full-screen mode
Example: sample assembler program for debugging
Defining a compilation unit as assembler and loading debug data
Deferred LDDs
Re-appearance of an assembler CU
Multiple compilation units in a single assembly
Loading debug data from multiple CSECTs in a single assembly using one LDD command
Loading debug data from multiple CSECTs in a single assembly using separate LDD commands
Debugging multiple CSECTs in a single assembly after the debug data is loaded
Halting when certain assembler routines are called
Identifying the statement where your assembler program has stopped
Displaying and modifying the value of assembler variables or storage
Converting a hexadecimal address to a symbolic address
Halting on a line in assembler only if a condition is true
Getting an assembler routine traceback
Finding unexpected storage overwrite errors in assembler
Customizing your full-screen session
Defining PF keys
Defining a symbol for commands or other strings
Customizing the layout of physical windows on the session panel
Opening and closing physical windows
Resizing physical windows
Zooming a window to occupy the whole screen
Customizing session panel colors
Customizing profile settings
Saving customized settings in a preferences file
Saving and restoring customizations between Debug Tool sessions
Terms of use
|
Feedback
This information center is powered by Eclipse technology. (http://www.eclipse.org)