Search VisualAge for Java Information Go to Information Home Page Go to VisualAge for Java WWW Site

Source pane

The behavior of the Source pane changes depending on the platform running the program you are debugging. Select the appropriate platform:

 

ngaix.gif (307 bytes)ngwin.gif (301 bytes) Source pane

Use the Source pane to view the content of your program as you debug it. The Source pane can display the source code for the program you are debugging in one of three ways: source code, disassembled machine code or a combination of the two. You can only view the source code for your program if your program was compiled with debug information.

The Source pane is split into two vertical columns. Your code appears in the right-hand column. The next line of code to be executed always appears highlighted in the right-hand column. The left-hand column contains line numbers that correspond to the lines of code in the right-hand column. This left-hand column is known as the prefix area. Colored numbers in the prefix area indicate that you can set a breakpoint on that line number.

The prefix area displays markers to show where breakpoints are set. A red dot (nbenbp.gif (97 bytes)) indicates an enabled breakpoint, while a gray dot (nbdisbp.gif (97 bytes)) indicates a disabled breakpoint. These dots do not necessarily indicate where you originally set a breakpoint, but rather where program execution will stop when the breakpoint is encountered. For example, if you set a function breakpoint, the dot will appear next to the first line of code within the function body, not the function declaration. The breakpoint indicator disappears when the breakpoint is deleted.

It is possible to have more than one breakpoint associated with a line of code, however, only one indicator will appear next to that line. The breakpoint indicator will disappear only when you have deleted all the breakpoints associated with that line.

The arrow (nbexept.gif (78 bytes)) in the prefix area indicates where items you have selected in other panes of the Distributed Debugger appear in your code. What the arrow indicates depends on the pane you are using:

if you click on... the arrow in the Source pane prefix area points to...
a function in the Stacks pane the line of code next to be executed in the function
a method in the Stacks pane the line of code next to be executed in the method
a breakpoint in the Breakpoints pane but not a deferred line or function breakpoint the location of the breakpoint in your code
an object file in the Modules pane the start of the source code for that object file
a function in the Modules pane the start of the function body
a class file in the Packages pane the start of the source code for that class file
a method in the Packages pane the start of the method body
an object file in the Object Modules pane the start of the source code for that object file
a procedure in the Object Modules pane the start of the procedure

When you issue a step command or run your program, the arrow will point to the next line of code to be executed.

 

ngos400.gif (278 bytes) Source pane

Use the Source pane to view the content of your program as you debug it. The Source pane can display the source code for the program you are debugging in one of three ways: Source View, Listing View or Statement View. You can only view the source code for your program if your program was compiled with debug information.

The Source pane is split into two vertical columns. Your code appears in the right-hand column. The next line of code to be executed always appears highlighted in the right-hand column. The left-hand column contains line numbers that correspond to the lines of code in the right-hand column. This left-hand column is known as the prefix area. Colored numbers in the prefix area indicate that you can set a breakpoint on that line number.

The prefix area displays markers to show where line breakpoints are set. A red dot (nbenbp.gif (97 bytes)) indicates an enabled line breakpoint, while a gray dot (nbdisbp.gif (97 bytes)) indicates a disabled line breakpoint. The breakpoint indicator disappears when the breakpoint is deleted.

The arrow (nbexept.gif (78 bytes)) in the prefix area indicates where items you have selected in other panes of the Distributed Debugger appear in your code. What the arrow indicates depends on the pane you are using:

if you click on... the arrow in the Source pane prefix area points to...
a thread in the Stacks pane the line of code next to be executed in the thread
a breakpoint in the Breakpoints pane the location of the breakpoint in your code
a module or class in the Programs pane the start of the source code for that module or class
a procedure or method in the Programs pane the start of the procedure or method body

When you issue a step command or run your program, the arrow will point to the next line of code to be executed.

 

ng390.gif (283 bytes) Source pane

Use the Source pane to view the content of your program as you debug it. The Source pane displays the source code view of the program you are debugging. The source code must exist in a permanent file or data set. When you debug your program, the actual program statements are shown in the Distributed Debugger as they are executing. To accomplish this, the data set input to the compiler is used. This might not be the original source, for example, if the program has been prepared by the CICS translator. The data set input to the compiler must be retained in a permanent data set. You can only view the source code for your program if your program was compiled with debug information.

The Source pane is split into two vertical columns. Your code appears in the right-hand column. The next line of code to be executed always appears highlighted in the right-hand column. The left-hand column contains line numbers that correspond to the lines of code in the right-hand column. This left-hand column is known as the prefix area. Colored numbers in the prefix area indicate that you can set a breakpoint on that line number.

The prefix area displays markers to show where breakpoints are set. A red dot (nbenbp.gif (97 bytes)) indicates an enabled breakpoint, while a gray dot (nbdisbp.gif (97 bytes)) indicates a disabled breakpoint. These dots do not necessarily indicate where you originally set a breakpoint, but rather where program execution will stop when the breakpoint is encountered. If you set a function breakpoint, the dot will appear next to the first line of code within the function body, not the function declaration. The breakpoint indicator disappears when the breakpoint is deleted.

It is possible to have more than one breakpoint associated with a line of code, however, only one indicator will appear next to that line. The breakpoint indicator will disappear only when you have deleted all the breakpoints associated with that line.

The arrow (nbexept.gif (78 bytes)) in the prefix area indicates where items you have selected in other panes of the Distributed Debugger appear in your code. What the arrow indicates depends on the pane you are using:

if you click on... the arrow in the Source pane prefix area points to...
a function in the Stacks pane the line of code next to be executed in the function
a breakpoint in the Breakpoints pane but not a deferred line or function breakpoint the location of the breakpoint in your code
an object file in the Modules pane the start of the source code for that object file
a function in the Modules pane the start of the function body
a class file in the Packages pane the start of the source code for that class file
a method in the Packages pane the start of the method body
an object file in the Object Modules pane the start of the source code for that object file
a procedure in the Object Modules pane the start of the procedure

When you issue a step command or run your program, the arrow will point to the next line of code to be executed.