Debug view

The Debug view displays the entry control block (ECB) system virtual address (SVA) address, execution point, and stack frames of the suspended ECBs for threads in active z/TPF debugger sessions. Use the Debug view to manage the debugging of your program.

The Debug view is provided by Eclipse and extended by TPF Toolkit. This topic contains information about this view that is specific to debugging ECBs on the z/TPF system. For more information about this view, see Debug view in the Eclipse documentation.

To open this view, take one of the following actions:
  • On the toolbar of the workbench, click the Debug icon.
  • Click Window > Show view > Debug

You can click a stack frame to show the associated source in the Editor view and local variables in the Variables view.

Choose the z/TPF debugger session to work with by clicking between debugger sessions. You can click between threads to choose the thread that you want to work with. Click the wanted thread before performing any actions.

For each thread, the execution point is displayed and then followed by the stack frame. The following lists the information that is shown for each element in the stack frame:
  • Function name
  • Object name
  • Optimization level
  • Debug information level
  • Module name
  • The loader level, which displays BASE or a loadset name if the program is loaded into the system
This view provides a toolbar for you to manage the debugging of your application. To display the toolbar, take one of the following actions:
  • Click Window > Appearance > Show Toolbar.
  • In the Debug view, click the View Menu icon, and click Show Debug Toolbar.

The toolbar provides the following options that are specific to debugging ECBs on the z/TPF system:

Debug UI daemon
Starts, stops, or changes the port number for the TPF Toolkit listener. You also can retrieve the workstation IP address that is known to the TPF Toolkit.
Step filtering/Step debug
Causes the step into button to behave as step debug. Step debug behaves similar to step into except that the z/TPF debugger stops only the application in modules that are in the step debug list. The step debug list is set by using the STEPDebug command in the debug console. The z/TPF debugger stops at all breakpoints; step over, run, and so on is unaffected.
Step into
Traces into the called function or the target Branch and Save-type instruction if the instruction is a function call or a BAS-type instruction in an assembler program. Otherwise it steps to the next sequential instruction.
Step over
Steps to the next sequential instruction but not into any function or BAS-type calls.
Terminate
Ends the application and all threads immediately; the application does not run to completion. Terminating an application can produce unpredictable results.
Disconnect
Detaches the z/TPF debugger from a running ECB. When you click this button, the ECB runs to completion, and does not stop at breakpoints, system errors, or ECB create events.

In the Debug view, right-click a stack frame, the displayed menu contains the following options that are specific to debugging ECBs on the z/TPF system:

Edit Source Lookup
Specifies a path used to locate the source file.
Properties
Shows details about the selected stack frame.
Show Stopping Thread
Shows the current execution point.
Options > Perform Heap Check on Stop
Informs the z/TPF debugger to verify that the application heap is not corrupted after the completion of any execute request (for example, step into or a breakpoint occurrence). If the heap of the application is corrupted, the debugger notifies you with a pop-up box. This feature might degrade performance of the z/TPF debugger.
Options > Stop at all function entries
Causes the z/TPF debugger to stop the application at the beginning of every function that is called.
Options > Stop at Null Pointers and Addresses
Causes the z/TPF debugger to stop the application and issue a debug engine message when a null pointer or null address detection event occurs.
Terminate and Remove
Terminates the debug session and removes the session from the Debug view.
The following list shows the scenarios that can stop the processing of a z/TPF application:
  • Breakpoints
  • CTEST
  • Manage compiled language event breakpoints
  • Timeout conditions
  • The following functions:
    • creec
    • credc
    • cremc
    • crexc
    • fork
    • swisc_create
    • tpf_cresc
    • tpf_fork
  • The following macros:
    • CREEC
    • CREDC
    • CREMC
    • CRESC
    • CREXC
    • SWISC TYPE=CREATE