unexplained repeatable Labview crashes

[Greg McKaskle]

It looks like a compiler bug that has since been fixed. I tried it on LV8.5.1 Mac version, and it runs fine when run on the directory of source you sent. I went past the breakpoint about eight times.

The crash log shows that an internal callback, part of the string processing library accessed bad memory when copying from one buffer to another. This almost certainly means that it was passed a bad parameter by the code LV generated.

So I can explain it, but I can't tell you a workaround -- because I can't reproduce it. My guess would be that you can jocky the string or cluster code around a bit, use shift registers instead of feedbacks, or something similar and you may be able to find a way of coding it that doesn't hit this error. Or better yet, see if you can find a newer version.

Greg McKaskle

[DonRotolo]

Are you having trouble downloading new code to the cRio? If so, PM me and I can try to explain an issue we identified and eventually showed to the NI team at championships.

Don

[Greg McKaskle]

This issue is with LV running on a Mac, so no RT download, no cRIO.

Greg McKaskle

[kamocat]

Thank you!
The shift registers successfully avoided the error.