LabVIEW executable not runnable when using asynchronous call

Question

Hello,
my project works fine from source, but fails to launch as an executable. I was able to track it down to the async call of an VI.
So far I was able to solve the problem by using a dummy queue and loop to be able to start the VI parallel to the rest of the code.
I tried:
1. mass recompile
2. build source distribution, remove existing build, create new one
3. allways include all callback VIs and all VIs called by reference through server
Still no success. I tried to lurk the forum for answers, but only found suggestion I already fail-tried. Please help
Solved!
Go to Solution.

Answer 1

ChazMasterFlash wrote:
My "conjecture" is that LabView does not handle references as rigourously as most computer languages.
I'm not entirely sure what you mean by that, but if I understand your sentiment, that's quite untrue. If anything, it's the opposite, as LV is quite strict in what it allows and how it handles things.
Also, regardless of the use (or lack of use) of locals to pass references around, writing code like that should not cause the issue described in this thread. At most, it should generate run-time errors. If you have something reproducible which causes this (particularly if you already found out how to handle it), I would suggest contacting NI support and giving them the code, so that they can find it and fix what needs fixing. Since your description was a vague "how I created the reference controls", I can't really say more than that.
ChazMasterFlash wrote:
Gawd I wish NI gave more direct use of pointers (which is essentially what a reference is). if I had access to address of the data, I think troubleshooting would be made much easier.
Am I alone here?
LV doesn't have pointers and probably never will, as that goes against the basic direction NI has gone with LV, which is to abstract and automatically handle all memory access. I don't think pointers would help you either, as they wouldn't mesh well with the way the rest of the language works. What you do have are various types of references, but references are NOT pointers. A pointers is simply an address of data in memory, without any additional data. A LV reference (which is different from a reference in C) is simply a "pointer" to a specific resource (control, VI, queue, event, etc.) which you can use with a specific API, and that's the key difference - any LV reference can only be used with a specific API, as opposed to a pointer, which is nothing more than an address.
The only real use case for pointers which I can think of in LV is to minimize data copies, but LV already tries to minimize data copies in different kinds of ways, including DVRs, which are not dissimilar to pointers (although they are NOT pointers). My guess would be that if you have difficulty with troubleshooting, then your code looks like C code written in LV, which can indeed be difficult to debug (and the locals comments also hints toward that direction).
Try to take over the world!