TADS Ada Static Dumper

Product Family: TADS
Target CPU: Any
Language: Ada
Host: Any

The Tartan Ada Static Dumper is a tool which provides developers with information about the variables, constants, packages, tasks, and subprograms that comprise a linked Ada program. This tool reads the AdaScope debug directives for a particular program and reports the locations of the objects which reside in constant (i.e., static) places in memory throughout the program's execution.

This information is most useful for connecting Tartan products to proprietary development systems using local hardware debug support. It is also quite useful for developers writing independent testing and analysis tools.

The static dumper produces a text file as its output. All names used in the output file are fully qualified Ada names. The format is designed to be easily read by users or parsed by programs. The output file may be printed on a wide (120 column) printer or in landscape mode on printers which support it.

Variables which are global to library level packages (whether exported or private) are reported. These variables are always stored at a fixed memory address. However, variables which are local to subprograms are not reported because they are relative to the frame pointer, and may be stored anywhere in memory.

Parameters and function return values are also listed. These values are usually in registers or relative to the frame pointer. Even so, this information should be used with care. The TADS Ada Compiler often uses copies of these values in the course of optimization.

Subprograms and other pieces of Ada code are listed if they have been linked into the program. In this case, the static dumper lists the addresses. These addresses include the first and last address in the code entity as well as the beginning and end of the Ada body code.

All constants and enumerated types in the program are listed in both their symbolic and actual value notations. Similarly, both notations are used for any arrays which are indexed by an enumerated type. Finally, the locations of all constants which could not be efficiently implemented by placing them in the code stream are indicated.