LabVIEW
DWarn 0x0E697B77 in ExtFuncRunTime.cpp
Something smells kinda fishy there. I wonder if the LabVIEW Runtime crashed? Look at all the unknown values.
When does this happen?
You probably first should debug those DLL calls more. Errors like the one you show can and often do happen because of badly configured Call Library Nodes (but a bug in the DLL itself is also not an impossible cause for such errors). Something is overwriting memory that it should not and that corrupts data structures which at some point cause LabVIEW to trip over its feet. This can happen right away after the corruption but often also only happens much later, as the data structures that got corrupted may not be accessed immediately after the execution of your DLL through the Call Library Node.
A very popular Call Library error that many LabVIEW programmers tend to do, is to NOT preallocated buffers to DLLs that the DLL is supposed to write data into. Unlike with LabVIEW VIs and nodes that allocate memory buffers (arrays, strings) anytime they are needed, a DLL can not do that in the same way as there is no managed contract about how to do that. The normal assumptions for most C functions is that the caller always provides any memory buffer that that function is expected to write into. LabVIEW programmers often tend to pass an empty string or array to a DLL function and expect it to automagically adjust that buffer to the size that the function wants in order to write its information into. This automagic however doesn't exist and can't exist. The function simply sees a pointer and has no way to know how large the allocated memory area is for this pointer. So the only thing it can do is to start writing into that buffer and if the buffer is smaller than the function needs to write into, it will write over the end of that buffer and overwrite (corrupt) data it has no business to touch.
