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

Locals pane

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

 

Locals pane

Use the Locals pane to view the contents of local variables that are in scope where your program has halted. This pane has entries for each thread in your program. The thread entries can be expanded to display all variables in scope for that thread. If that variable has subelements, such as an array or a class, it can be expanded to display the subelements.

Pop-up menu options allow you to enable or disable, edit, delete and change the representation of variables in this list.

When you enable, disable or delete a variable in the list, the action only affects the variable while you are in the present scope. Once the scope changes, the list of variables will be updated with all the variables now in scope.

Enabled variables are indicated with a red diamond (nbvaren.gif (91 bytes)). Disabled variables are indicated with a gray diamond (nbvardis.gif (76 bytes)).

Leaving threads expanded in the Locals pane may affect the performance of the Distributed Debugger. The local variables associated with a thread may be updated during program execution if the threads are expanded. Variables can be updated from a change in scope, a program step or from the function on top of the call stack. If you find performance of the Distributed Debugger is slow while stepping through your program, completely collapse the threads in the Locals pane.

 

Locals pane

Use the Locals pane to view the contents of local variables that are in scope where your program has stopped. This pane has entries for each thread in your program. Each thread number can be expanded to display the *LOCALVARS data structure. The *LOCALVARS data structure can then be expanded to display all variables in scope for that thread. If a local variable has subelements, such as an array or a class, it can be expanded to display the subelements. Pointers and Java object references can be dereferenced, which causes a new expression to be added to the Locals pane.

Pop-up menu options allow you to enable or disable, edit and delete variables in this list.

Enabled variables are indicated with a red diamond (nbvaren.gif (91 bytes)). Disabled variables are indicated with a gray diamond (nbvardis.gif (76 bytes)).

Leaving threads expanded in the Locals pane will affect the performance of the Distributed Debugger. The local variables associated with a thread may be updated during program execution if the threads are expanded. Variables can be updated from a change in scope or a program execution. If you find performance of the Distributed Debugger is slow while stepping through your program, completely collapse the threads in the Locals pane.

 

ng390.gif (283 bytes) Locals pane

Use the Locals pane to view the contents of local variables that are in scope where your program has halted. This pane has entries for each thread in your program. The thread entries can be expanded to display all variables in scope for that thread. If that variable has subelements, such as an array or a class, it can be expanded to display the subelements.

Pop-up menu options allow you to enable or disable, edit, delete and change the representation of variables in this list.

Another pop-up menu option lets you display the contents of a selected storage block according to a user-defined layout specified in an XML file. This pop-menu option is not available when debugging interpreted Java programs.

When you enable, disable or delete a variable in the list, the action only affects the variable while you are in the present scope. Once the scope changes, the list of variables will be updated with all the variables now in scope.

Enabled variables are indicated with a red diamond (nbvaren.gif (91 bytes)). Disabled variables are indicated with a gray diamond (nbvardis.gif (76 bytes)).

Leaving threads expanded in the Locals pane may affect the performance of the Distributed Debugger. The local variables associated with a thread may be updated during program execution if the threads are expanded. Variables can be updated from a change in scope, a program step or from the function on top of the call stack. If you find performance of the Distributed Debugger is slow while stepping through your program, completely collapse the threads in the Locals pane.