Entering Break Mode at a Problem Statement

See Also

Break mode halts the operation of an application and gives you a snapshot of its condition. Variable settings are preserved, so you can analyze the current state of the application and enter changes that affect how the application runs. When an application is in break mode, you can:

• Modify code in the application.
  
  
• Observe the condition of the application's interface.
  
  
• Determine which active procedures have been called.
  
  
• Watch the values of variables, and expressions.
  
  
• Change the values of variables.
  
  
• View or control which statement the application will run next.
  
  
• Run statements immediately.
  
  
• Manually control the operation of the application.

To enter break mode at run time

• Choose Break from the Debug menu.

  It's possible to break execution when the application is idle (when it is between processing of events). When this happens, execution stops when the next line of code is run.

  -or-

• Set a breakpoint in your code in the Text Editor window or define a breakpoint in the Breakpoint dialog box.

  When the program encounters a breakpoint at run time, it will enter break mode before executing the line of code where the breakpoint was set.

  -or-

• Programmatically place a statement in your code. The command for entering break mode varies by language. For more information about a specific language, see the debugging topics for that language.

To enter break mode at design time

• Select Step Into from the Debug menu.

  Break mode will be entered at the first line of code in your application.

  -or-

• Select Run to Cursor from the Debug menu.

  The application will enter break mode when it reaches the current line of code in the Text Editor window.

  The exact behavior of break mode may differ slightly for different language engines or certain types of applications. For more information, see the debugging topics for your programming language.