Run menu

The Run menu contains commands for running and debugging your program. Choose one of the following commands for more information.



Run|Run Project

Runs your application without debugging it, using parameters specified in the Run page of the Project Properties dialog box.

Alternate ways to perform this command are:

When you choose Run|Run Project, JBuilder automatically compiles the file or project before running it, if the Compile Before Running option is set on the Run page of the Project Properties dialog box.

Use the Project Properties dialog box (Project|Project Properties) to change compiler options. When working with partial projects, make sure that the Make Stable Packages option is unchecked.

See also


 
 

Run|Debug Project

Runs your application in the debug mode.

When you choose Run|Debug Project, JBuilder automatically compiles the file or project before debugging it, if the Compile Before Debugging option is set on the Run page of the Project Properties dialog box.

To place symbolic debugging information into the class files, use the Include Debug Info option on the Compiler page of the Project Properties dialog box. (This is the default.)

When you start the debugger, the debugger user interface displays in the message pane below the AppBrowser. For more information, see the topic called "Debugger user interface."

Alternate ways to perform the Debug command are:

See also



Run|Run Class

Runs your class without debugging it, using parameters specified in the Run page of the Project Properties dialog box.

This command is only available if the class open in the editor is runnable.

When you choose Run|Run Class, JBuilder automatically compiles the file before running it, if the Compile Before Running option is set on the Run page of the Project Properties dialog box.

Use the Project Properties dialog box (Project|Project Properties) to change compiler options. When working with partial projects, make sure that the Make Stable Packages option is unchecked.

See also


 
 

Run|Debug Class

Runs the class open in the editor in the debug mode.

When you choose Run|Debug Class, JBuilder automatically compiles the file before debugging it, if the Compile Before Debugging option is set on the Run page of the Project Properties dialog box.

To place symbolic debugging information into the class file, use the Include Debug Info option on the Compiler page of the Project Properties dialog box. (This is the default.)

When you start the debugger, the debugger user interface displays in the message pane below the AppBrowser. For more information, see the topic called "Debugger user interface."

Alternate ways to perform the Debug command are:

See also



Run|Configurations

Displays the Runtime Configurations dialog box where you set up runtime configurations.

See also


 
 

Run|Step Over

Runs your application or applet one line at a time. If Smart Step is on, classes in the Classes with tracing disabled view will not be stepped into. When off, all classes are stepped into.

The debugger treats multiple statements on one line of text as a single line of code; you cannot individually debug multiple statements contained on a single line of text. The debugger also treats a single statement that spans several lines of text as a single line of code.

By default, when you initiate a debugging session with Run|Step Over, JBuilder moves the execution point to the first line of code that contains debugging information (this is normally a location that contains user-written code).

In addition to stepping over methods, you can trace into them as well. Use Run|Step Into to step into each line of a method call.

Alternate ways to perform the Step Over command are:

See also


 
 

Run|Step Into

Runs your application or applet one line at a time, stepping into methods while following the execution of each line. If Smart Step is on, classes in the Classes with tracing disabled view will not be stepped into. When off, all classes are stepped into.

The Step Into command executes the statement highlighted by the execution point and advances the execution point to the next executable statement.

By default, when you initiate a debugging session with Run|Step Into, JBuilder moves the execution point to the first line of code that contains debugging information (this is normally a location that contains user-written code).

In addition to tracing into methods, you can step over them, executing each method as a single element. See Run|Step Over for more information.

Alternate ways to issue the Step Into command are:

See also


 
 

Run|Step Out

Steps out of a method to the calling routine.

Classes in the Classes with tracing disabled view will not be stopped in. It is possible to be in this situation, for example, when you step out of routine that was called from a class you didn't want to step into.

An alternate way to issue this command is to click the Step Out icon    on the debugger toolbar.


 
 

Run|Run To Cursor

Runs your application up to the location of the cursor in the source pane. When you run to the cursor, your application runs at full speed, then pauses and places the execution point on the line of code containing the cursor.

You can use Run To Cursor to run your application and pause before the location of a suspected problem. You can then use Run|Step Over or Run|Step Into to control the execution of individual lines of code.

See also


 
 

Run|Run To End Of Method

Runs your application at full speed until it reaches the end of the current method.

See also


 
 

Run|Pause Program

Temporarily pauses the execution of a running application.

The debugger pauses and positions the execution point on the next line of code to run. You can examine the state of your application at this point, then continue debugging by running, stepping, or tracing.

In addition to temporarily pausing an application or applet running in the debugger, you can also stop it and release it from memory by choosing Run|Program Reset, or pressing Ctrl+F2.

See also


 
 

Run|Resume Program

Continues the current debugging session or restarts one that has finished or been reset.

Alternate ways to issue the Resume command are to:

See also


 
 

Run|Reset Program

Ends the current application run and releases it from memory.

Use Reset to restart an application from the beginning, such as when you make a change to the code and want to run again from the beginning, or if variables or data structures become corrupted with unwanted values.

When you reset an application, JBuilder performs the following actions:

Resetting an application does not delete any breakpoints or watches you have set. This makes it easy to resume a debugging session.

An alternate way to issue the Reset command is to click the Reset icon    on the debugger toolbar.

See also


 
 

Run|Show Execution Point

Positions the cursor at the execution point in the content pane. If you close the window containing the execution point, JBuilder reopens it the next time you choose Run|Show Execution Point.


 
 

Run|Evaluate/Modify

Opens the Evaluate/Modify dialog box, where you can evaluate or change the value of an existing method, expression or property. You can evaluate any valid language expression.

The Evaluate/Modify dialog box lets you view and modify the values of object properties while the program is suspended. However, to view a property, you need to explicitly specify the property name. For example, you can enter the following expression to evaluate the Caption property of Button1:

Button1.Caption

Alternate ways to perform an Evaluate|Modify command are:

See also


 
 

Run|Add Watch

Opens the Add Watch Expression dialog box, where you can add a name watch and specify its properties. A name watch is added on a name - as you move around in your code, whatever variable has the name you selected in the current context will be the one evaluated for the watch.

The Data watches view displays the watches and lets you add, edit, delete, enable, and disable watches from its context menu.

Alternate ways to perform the Add Watch command are to:

See also


 
 

Run|Add Breakpoint

Displays a drop-down menu where you choose the type of breakpoint to add. You can add a:

No matter what type of breakpoint you choose to add, the Breakpoint Properties dialog box is opened, where you can create and modify breakpoints.

Note: When you're adding breakpoints, the title on this dialog is "Add <Breakpoint Type> Breakpoint."

A breakpoint is a place in your program where execution temporarily stops. When the debugger reaches a breakpoint, it pauses your program. You can specify any number of breakpoints in your code.

When you set a breakpoint, the line on which the breakpoint is set becomes highlighted, and a stop-sign glyph appears in the left margin of the breakpoint line.

Each breakpoint listing shows the following in the Data and code breakpoints view:

Alternate ways to perform the Run|Add Breakpoint command are to:

See also


 
 

Run|View Breakpoints

Displays the Breakpoints dialog box, the list of breakpoints that are set for the current debugging session.

See also


 
 

Run|View Classes With Tracing Disabled

This is a feature of JBuilder Professional and Enterprise.

Displays the Classes With Tracing Disabled dialog box, the list of classes for which tracing has been disabled.

See also