LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LV8.01: Bug when casting in "build array"

I have had another change to look at the second VI which produces incorrect results.  Looks like the corruption that causes LabVIEW to crash in the first VI posted to this thread does some wicked things to the for loop instead of causing a crash. 

I ran the VI with hi-lite execution and noticed that the for loop only executes once, so that explains why only the first page of the result array is correct, and the "correct array" matches the first page of the erroneous array rather than the last page (the array should only pass out the last value).  I passed this information along to R&D. I did not create a new CAR because these issues (crash and incorrect results) are tied to the same root cause. 

Cheers,
Spex
National Instruments

To the pessimist, the glass is half empty; to the optimist, the glass is half full; to the engineer, the glass is twice as big as it needs to be has a 2x safety factor...
0 Kudos
Message 11 of 12
(679 Views)

@Spex wrote:
Looks like the corruption that causes LabVIEW to crash in the first VI posted to this thread does some wicked things to the for loop instead of causing a crash. 

I agree. I think this is a buffer overflow when allocating memory for the array. That's why it can do all kinds of weird stuff.

"This was reported to R&D (#43Q7NJPT) for further investigation."

Thank you all very much. Hope this get's fixed - ah well this will mean another update and another mass compile Smiley Indifferent.
0 Kudos
Message 12 of 12
(670 Views)