You must compile files before running them. This places symbolic debugging information into the file so the Debugger can operate.
When you select Debug, the AppBrowser switches into Debugger mode. In Debugger mode, you use the Content pane for viewing code and setting breakpoints. The Debugger mode also displays panes for viewing data watches and context information such as call stacks and threads.
Alternate ways to perform the Debug command are:
See also:
Building Applications with JBuilder: Debugging Java programs
Building Applications with JBuilder: Overview of the debugging process
An alternate way to perform this command is to click Run on the toolbar.
Files must be compiled before they can run. When you choose Run|Run, JBuilder automatically compiles the file or project before running it.
Use the Project Properties dialog box (File|Project Properties) to change compiler options. When working with partial projects, make sure that the Make Packages Stable option is unchecked.
See also:
Building Applications with JBuilder: Compiling Java programs
See also:
Building Applications with JBuilder: Sending command-line arguments to your program
Building Applications with JBuilder: Setting environment variables
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 procedures, you can trace into them as well. Use Run|Trace Into to execute each line of a procedure.
An alternate way to perform the Step Over command is to press F8.
See also:
Building Applications with JBuilder: Stepping over a method call
The Trace Into command executes the statement highlighted by the execution point and advances the execution point to the next statement.
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.
An alternate way to perform the Trace Into command is to press F7.
See also:
Building Applications with JBuilder: Tracing into a method call
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|Trace Into to control the execution of individual lines of code.
See also:
Building Applications with JBuilder: Running to the cursor location
See also:
Run|Run To Cursor
Building Applications with JBuilder: Running to the end of a method
See also:
Building Applications with JBuilder: Finding the execution point
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.
If your application or applet assumes control and does not return to the Debugger--for example, if it is running in an infinite loop--you can press Ctrl+Alt+SysRq to stop your application. You might need to press this key combination several times before your program actually stops.
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:
Building Applications with JBuilder: Pausing the program
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 JBuilder
If your system becomes unstable, through either multiple hardware or language exceptions, or through a loss of system resources as a result of resetting a program, exit and restart JBuilder before restarting the debugging session.
See also:
Building Applications with JBuilder: Restarting the program
Alternate ways to perform the Add Watch command are,
See also:
Building Applications with JBuilder: Watching expressions
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 Breakpoint List window:
You can also add a breakpoint in one of the following ways:
To edit a breakpoint, in the Breakpoint List window, right-click an existing breakpoint and choose Edit Breakpoint.
See also:
Building Applications with JBuilder: Using breakpoints
UBuilding Applications with JBuilder: Setting breakpoints
See also:
Building Applications with JBuilder: Inspecting data elements
Button1.Caption
See also:
Building Applications with JBuilder: Evaluating expressions