OpenAccess SDK uses the trace function to allow function calls, arguments, and other messages to be displayed based on a flag provided at runtime. The tm_trace function provides a flexible way to trace events because it is possible to set different levels of tracing with total control over enabling or disabling at runtime. Output of the trace can go to the display or file or to both.
Insert as many traces as possible, specifically for each error or important event occurring, as well as for each assumption or minor event occurring. Function calls should be traced by placing a trace as the first instruction of each function (using the flag UL_TM_F_TRACE to trace the program flow). Additionally, IP identification and version information should be displayed by the IP initialization routines (using the flag UL_TM_INFO) to facilitate future maintenance. For information about how to control tracing, refer to the OpenAccess SDK Troubleshooting Guide and Reference. The ServiceIPLogOption service attribute controls the tracing level. Log files for each connection are stored in the install_dir/logging directory.
