What causes "A Run-State Change Callback" protection fault.

[VIagra]

Hello!,
I'm maintaining some DAQ C++ code that I didn't write and it has an odd bug... Whenever we close the application, an error dialog appears with "LabWindows CVI" in the title-bar. The error text is "A Run-State Change Callback caused a protection fault." When compiled, the app. _probably_ draws from some ni device-driver, or one that was built with LabWindows CVI. Anyway, I'd like to make this dialog go away. Any ideas are appreciated!

[Chris Matthews]

Run State change Callbacks are discussed in our CVI manuals and our Knowledgebase here. I couldn't really say why your application is getting a protection fault in the callback, but you must be using the CVI run-time engine. The callback was used in the CVI envinronment for determining the run-state in debugging.

Hope that information helps,

Chris Matthews
National Instruments