[DjScribbles]

The probable cause is that the compiler in windriver for vxWorks is very permissive of function names (and class names?) at compile time, and doesn't give a warning or error when it doesn't see a function you are referring to; instead it assumes that the function will be available at runtime on the cRio.

The result is that if you call functions (not methods of classes, which IIRC do get checked, since they are scope limited, but don't quote me on that), but have spelling/case errors, the compiler assumes it is an intentional reference to something it doesn't know about. In other cases, calling general library functions (such as itof) can cause this, since the library isn't on the cRio.

When you encounter this from an innocuous change, look at what has changed very carefully, and look at what may have changed in your runtime code path as the result of the change, since the problem could be in code you've had for a while, but don't typically call.