CHorn

My guess is that it's some kind of buffer overflow when allocating memory for the array that uses automatic type casts. This would explain why sometimes weird stuff happens and sometimes it crashes. In this example the loop gets "damaged". http://forums.ni.com/ni/board/message?boar...ssage.id=217205 I think this is a very grave bug. Fortunately it is restricted to certain input configurations and to the combination of complex double with integers (all kinds) and singles. I didn't test very thoroughly though. Christian

When wiring variables of different types into a "build array" function, i.e. when automatic type casting is used, LV can crash completely or the resulting array can contain incorrect values. The details depend on the exact configuration of the input for the build array function. LV 8.01 and LV 8.20 (I discovered this using 8.01) seem to be affected on WinXP, Mac OSX (PPC) seems to be not affected. This is a pretty nasty bug because instead of crashing it can result in incorrect numeric results and is then really hard to allocate because usually one does trust really essential basics of the programming language like automatic type casts. P.S.: I posted this already in the NI forums but I thought this might be interesting...Download File:post-6991-1164671256.viDownload File:post-6991-1164671267.vi