LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview Bug?!?

Think I may have found a bug. Comments please. Follow this link for
the code:

http://yourpage.blazenet.net/ninnurta/labviewbug3.vi

This link refers to a vi that was written with Labview 6.0.2, but I
have seen the same behavior in 5.1. Is this normal functioning?? I
have a program that has this same basic structure, although I am not
using empty array constants to control the inner loops. I do have
instances where loop control arrays are empty, though and saw the
behavior in this instance.

greenman
0 Kudos
Message 1 of 2
(2,605 Views)
This is not a bug. Non-indexing outputs of a loop that do not execute are
undefined. Execute the VI in debugging mode and you will see that the wire
exiting For Loop 2 has no data source and then returns any garbage left
there by previous memory usage. You fix this outputting the value in a shift
register properly initialyzed.

See attached fix.

Jean-Pierre Drolet
Scientech R&D

"greenman" a écrit dans le message news:
1a51ebaa.0106221216.2afb8bf0@posting.google.com...
> Think I may have found a bug. Comments please. Follow this link for
> the code:
>
> http://yourpage.blazenet.net/ninnurta/labviewbug3.vi
>
> This link refers to a vi that was written with Labview 6.0.2, but I
> have seen the same behavior in 5.1. Is this nor
mal functioning?? I
> have a program that has this same basic structure, although I am not
> using empty array constants to control the inner loops. I do have
> instances where loop control arrays are empty, though and saw the
> behavior in this instance.
>
> greenman



[Attachment nolabviewbug3.vi, see below]


LabVIEW, C'est LabVIEW

Message 2 of 2
(2,605 Views)