Using the Desktop Execution Trace Toolkit

You can use the Desktop Execution Trace Toolkit to debug and optimize large LabVIEW applications, including those with multiple loops, client-server architectures, dynamically-loaded VIs, and so on. The toolkit captures execution events from applications running on the desktop of a local or remote computer and displays the execution events in the table pane.

You also can use the Desktop Execution Trace Toolkit to debug stand-alone applications and shared library files that you create using the Application Builder. However, the toolkit cannot trace a LabVIEW-built shared library (DLL).

Note  The LabVIEW Professional Development System includes the Application Builder. If you use the LabVIEW Base Development System or Full Development System, you can purchase the Application Builder separately by visiting the National Instruments website. Refer to the LabVIEW Help for more information about the Application Builder.

Trace Data

The execution events that the Desktop Execution Trace Toolkit captures from LabVIEW applications are called trace data. You can browse the trace data in the table pane, save the trace data in execution trace (.det) files, or export the trace data to text (.txt) files.

Trace Sessions

When you use the Desktop Execution Trace Toolkit to capture trace data from a LabVIEW application, you are executing a trace session. A trace session is the period of time between when you click Start and Stop in the Desktop Execution Trace Toolkit. During this time, the toolkit captures trace data from LabVIEW applications or VIs that run in the application instance you select from the Application Instance pull-down menu on the Home tab.

Trace Procedures

Tracing a LabVIEW application instance, a VI that runs in the application instance you select, a LabVIEW stand-alone application, or a shared library file typically involves the following steps:

1. Opening a trace connection to a LabVIEW application instance.
2. Configuring a trace session to capture relevant data.
3. Executing a trace session.
4. Reviewing trace data that appears in the table pane.
5. Comparing trace data between two sessions of one or two traces.
6. Saving or exporting trace data.