VI class/Execution.Allow Debugging property

From LabVIEW Wiki
Jump to: navigation, search
VI Server Property Information
Property ID 206
Scope Basic Development Environment
Data Name Exec.AllowDebug
Short Name* Exec.AllowDebug
Long Name* Execution:Allow Debugging
* Displayed here in English. Short and Long names appear in the language of the LabVIEW IDE.
Owning Class ID 2
Owning Class Name VI Class
Data Type Boolean data type


Property Node Execution:Allow Debugging
Available in Real-Time Operating SystemYes
Available in Run-Time EngineYes (Read Only)
Available with control VIsNo
Available with global VIsNo
Available with polymorphic VIsNo
Available with strict type definitionsNo
Loads the block diagram into memoryNo
Loads the front panel into memoryNo
Must wait until user interface is idleNo
Need to authenticate before useNo
Remote access allowedYes
Settable when the VI is runningNo

If TRUE, you can use debugging tools on the VI. For example, you can set breakpoints, create probes, enable execution highlighting, and single-step through execution. Set this property to FALSE to disable use of debugging tools, reduce memory requirements, and to improve performance slightly for the VI.

This property is similar to the Allow debugging option on the Execution page of the VI Properties dialog box.

Note Writing this property causes the VI to be recompiled. Writing TRUE causes extra code and data to be generated for the VI. This code and data enables LabVIEW to set breakpoints and single-step through the VI. Writing FALSE removes this code and data, reducing the total size of the VI.

When you debug applications and shared libraries, you cannot debug reentrant panels that an Open VI Reference function creates. You also cannot debug reentrant panels that are entry points to LabVIEW-built shared libraries.



Version Change(s)
LabVIEW 2018 More info to come.

See Also

External Links