This bug seems to restricted to the attached code. Any change to the VI block diagram which in turn marks the VI changed
in the title bar with an asterisk. If I try to run the VI in its
unsaved state it crashes with the VIExecState.cpp Line 530 error.
This is how I induce the fault using the attached code.
1. Before starting LabVIEW add "DWarnDialog = TRUE" to the LabVIEW.ini file without the quotes.
2. Open "BurnIn Shelf 2 - Shell Only.vi"
3. Click the "Run" toolbar icon code then click "Abort Execution".
4. Edit the block diagram e.g. add a free label.
5. Click the "Run" toolbar icon again.
6. This should induce the VIExecState.cpp, Line 530 error.
As this is a "warning" I have set "DWarnDialog = TRUE" in the LabVIEW.ini before starting labview. This means any warnings not critical to execution are displayed immediately. They are normally kept hidden until you start labview. Unfortunately, things like occurence notification stop working so its critical to some of my code implementations. Remove this entry from your labview.ini if you have finished debugging.
I have not found the source of the issue in my code yet. The error has been reported to NI UK. CAR reference for this error is #45703. I will keep the forum informed of any developments.
David
Message Edited by David Crawford on
04-07-2008 04:19 PM
