Debugging an Application

Use the PowerScript Debugger to identify and resolve logic and semantic errors that occur when you run your application.

Debugging is usually an iterative process: you run the debugger to evaluate your application's execution and diagnose problems in your code. After editing your code to fix the problems, run the debugger again to test your fixes. You might repeat this cycle many times.

This is a single iteration in a typical debugging cycle:

  1. Insert breakpoints where you suspect problems might occur.
  2. Run the application in debug mode, either stopping at breakpoints, or stepping through one line at a time.
  3. Each time execution stops, use debugger functions to examine the context of the application, such as coding logic, the values of variables, or the call stack. You can add or modify breakpoints while your application runs, and test the effects of different variable values on execution.
  4. To fix problems that you discover during debugging, stop the debugger and edit your application in design mode.
Related concepts
PowerBuilder .NET Debugger Changes
Related reference
Debug Windows