Can Inlined SubVIs Be Included in the Internal Crash Report?

Updated Feb 13, 2019

Reported In

Software

  • LabVIEW

Issue Details

I have included several inlined subVIs in my code. When I get the internal crash report I cannot see from which inlined subVIs the error is coming. Is there a way to include the inlined VIs in the LabVIEW Log Report?

Solution

Inlining a subVI removes the need to call the subVI at run time. LabVIEW executes the subVI code inside the compiled code of the calling VI. This is the reason why you then must recompile every time you make changes to an inlined VI.
Because of this, once the code start running, LabVIEW is not able to recognise the part of the code coming from the inlined VIs against the rest of the main VI.

If the execution time is not important, one alternative could be Building Polymorphic VIs which are not inlined.
 

Additional Information

For further information about inlined VIs, please refer to the SubVI Overhead section of the VI Execution Speed article.

If you want to know more about Polymorphic VIs, please check the Polymorphic VIs documentation on our website.

WAS THIS ARTICLE HELPFUL?

Not Helpful