Touring AreasTour Areas: [1] Minimal Source Code Instrumentation

[5. Running the Logging Server ]
[6. View Data, Live and Recorded]
[7. The Data ]
[8. Reviewing Data ]
[9. The Documentation]

[3] Compiling the Tapped Application

After a set of DTraq.Tap instantiations have been made, and the calls to those procedures inserted into the code, the application needs to be rebuilt.

When compiling and linking a tapped application the DTraq include and /lib directories must be supplied to the compiler, along with either the static or dynamic versions of the DTraq library (libdtraq.a or

For example, if using GNAT's gnatmake utility, and the original command for compiling an application was:

$ gnatmake dtraq_logging_example

Assuming that an environment variable named "DTRAQ" has been defined whose value is the directory in which DTraq was installed, then the command for compiling the tapped application would be:

$ gnatmake -I$DTRAQ/include dtraq_logging_example.adb -largs -L$DTRAQ/lib -ldtraq


The resulting application can then be run as usual, but this time the tapped data items are transmitted to the the logging server for logging--which also makes them available for live monitoring through the client data viewer while the program is actively running.

Next: Scanning the Source Code


©2006 McKae Technologies