![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Using the Show Data Dialog BoxThe Show Data dialog box is displayed by the Debug > Show... command (executed from any debugger window). The data appears in the Debugger window.
The Show Data dialog box is also displayed by the Debug > Display... command. In this case, the data appears in the Object Display window.
In the Expression field, enter the name of a program variable, subprogram name, function, class, task entry name or arithmetic expression whose value is to be displayed. For an object, use the debugger pathname. Note that an expression is a formula that defines the computation of a value. Expressions are evaluated using the programming language grammar rules.
For Ada variables, the debugger currently supports simple variable names (MARK, R_A) selected components and expanded names (MARK.LINE), strings (DATE 1..4) and indexed components (X(Y), Z(1,2)). Also, use these in combination (X(M.Z), B.X(1)). The debugger supports the evaluation and display of Ada array slices (for example, p date (1..3)).
Ada subprograms and C/C++ functions and classes can be called. You can use the results of a function in the expression. Some restrictions exist. Only parameters of mode in are supported. in out or out parameters are not supported. Default parameter values are not yet supported. Functions returning access values can be called. In addition, functions that return composite types, (for example, arrays, records) can also be called. Arbitrary return types when the function is not inside of a larger expression are also supported. Only functions that return type STRING can be used inside a larger expression (and then only if the result is small enough (<= 512 bytes).
A parameterless function must be called using empty parentheses. When referencing a subprogram or function, it may be necessary to resolve overloading.
Ada entry calls can be called. The calls are not made immediately but instead are queued by the debugger task. When the user program is set into motion the debugger spawns a new caller task for each entry call which performs the rendezvous. This allows blocked entry calls to not cause deadlock in the debugged application. Only parameterless entry calls are currently supported.
The debugger uses visibility rules similar —— but not identical —— to Ada or C/C++ for looking up variable names. The current frame determines what names are visible. The visible names are the same names that are visible if a statement is added to the program at the point in the source text corresponding to the current frame.
In the Levels field, enter the number of levels to evaluate for structured objects.
Select the Expand Pointers option to dereference pointers. The Levels value is used to determine the depth of traversal.
Select the Special Type Display option to use your customized display function.
Select the Show Location option to also display the location of the object (a register number or a memory address for an object or nothing for a computed expression).
The Levels, Expand Pointers, Special Type Display, and Show Location options use the current value of the corresponding debugger option as the default and set the corresponding debugger option when okayed or applied. Use the View > Options command to view and/or modify these debugger options.
Additional information on displaying data can be found in Using the Apex Debugger.
Rational Software Corporation http://www.rational.com support@rational.com techpubs@rational.com Copyright © 1993-2001, Rational Software Corporation. All rights reserved. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |