LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

GPF 001B:631065BB while compiling project in LabWindows/CVI 5.5

When I try to Compile and Run a project in LabWindows/CVI 5.5 on Windows 2000 I get the following message "run time error (cvi) This program has caused a first chance "General Protection" Fault at 001B:631065BB"

any idea on how to solve this?

Thanks
0 Kudos
Message 1 of 3
(3,107 Views)
This may or may not be a problem. With CVI 5.5 simply go to "options>run options" and turn off "break on first chance exceptions". That's what everyone here does!

Except for me.... What I would suggest is find out where the exception is being thrown and if it is a problem fix it and if it is not use "SetBreakOnFirstChanceExceptions" to temporarily disable this feature.

See help from below:

SetBreakOnFirstChanceExceptions
int SetBreakOnFirstChanceExceptions (int newState);

Purpose
If debugging is enabled, this function controls whether LabWindows/CVI displays a run-time error dialog box and suspends execution when a first-chance exception occurs.

In general, use the Break on�First Chance Exceptions option in the Workspace window to control this feature. Use this function when you want the temporarily disable the Break on�First Chance Exceptions feature around a segment of code. SetBreakOnFirstChanceExceptions changes the setting for the thread that calls SetBreakOnFirstChanceExceptions.

Example
int oldValue;
oldValue = SetBreakOnFirstChanceExceptions (0);
/* function calls that may legitimately return errors */
SetBreakOnFirstChanceExceptions (oldValue);

This function does not affect the state of the Break on�First Chance Exceptions option in the Workspace window.

If debugging is disabled, this function has no effect. Run-time errors are never reported when debugging is disabled. Debugging is enabled when you set the debugging level in the Build Options dialog box of the Workspace window to Standard or Extended.

Parameters
Input
Name Type Description
newState integer Determines whether the Break on first chance exceptions feature is enabled on disabled.

If the value is non-zero, LabWindows/CVI displays a dialog box and suspends execution when a first-chance exception occurs. If the value is zero, LabWindows/CVI does neither.

If debugging is disabled, this parameter has no effect.

Return Value
Name Type Description
previousState integer The previous state of the state of the Break on first chance exceptions option. When debugging is disabled, 0 is always returned.

Code Description
1 Break on first chance exceptions is enabled.
0 Break on first chance exceptions is disabled.
0 Kudos
Message 2 of 3
(3,107 Views)
Hi,
you say you get a GPF (not a break as Joe's answer would solve). In other words, CVI itself shuts down, because it's errored in windows.
If you just try to compile and link (but not run) the project does it GPF?
If you try with one of the small shipping examples, does that cause a problem?
Are you doing stuff with a UIR at the time of running (if it's working OK compiling and linking, but GPF's when running). (the 001B area could suggest UIR issues - no guarantees on that though).
Make sure your paths to the uir when using LoadPanel are less than 169 characters.
Also, if you can compile and link, then set cvi to break at first command, and step through the code until the error occurs.

Hope that helps
Thanks
Sacha Emery
National Instruments (UK)


Thanks
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer Smiley Wink
0 Kudos
Message 3 of 3
(3,107 Views)