02-21-2012 07:06 AM
I am building an application in Labview 2010 Professional (upgraded to the latest patch, f4)
The application builds successfully, but when I start my built application, it crashes instantly (on the same computer I built it on) reporting a crash in lvrt.dll
I have tried omitting parts of the code that accesses dll files but that didn't help. I am not able to use remote debugging since it crashes instantly.
First I was able to build and run the application on my developement computer, but not run it on the deployment computer. Later I was not able to run on the developement computer either, I had not made huge alterations of the code so I do not know what the difference is.
Now I am building it on a new installation of Labview 2010 Professional on the deployment computer and can not run it on either computer. I use some Open G vis, installed through VIPM, nothing else special.
How should I continue my troubleshooting, does anoyone have any suggestions?
Solved! Go to Solution.
02-21-2012 08:01 AM
In the build you could try configuring VIs that execute during initialization to open their front panels when called. This would tell you if the crash occurs before your code starts or how far the code actually gets before blowing up. Also can you extend what you have already done by throwing disable structures around things to disable everything but the basic logical structure (state machine, event handler, whatever...)? It the application all in one piece or are there processes that run in the background?
Mike...
02-23-2012 06:24 AM - edited 02-23-2012 06:26 AM
Thanks! I had started to disable some parts of the code but I was to lazy to do it thoroughly. By doing it systematically like you suggested I was able to pinpoint the problem. It was not where I hade expected at all. It seems a small vi "Create new report" from the Report generation toolkit is corrupted, causing the whole application to crash.
05-16-2012 12:19 PM
Very helpful topic. My project had instant crashes also after modifying shared variable.
I have set the initialization VIs to open their front panel when running (Ctrl+i << Window Appearance). They would not show, meaning the program didn't even run.
I have used disable structures to isolate the problem. Some odd parts in the code were isolated in the process (a Build Array node, for example), but one of the isolated parts was a sub-VI containing the shared variable I had modified. Opening and saving that particular sub-VI fixed the issue. The other odd parts I had isolated didn't bug anymore when I enabled them.
Thanks!