CVI 2010 SP1 Crash

[snoop]

Hallo, ich habe ein Update von CVI 2009 auf CVI 2010 durchgeführt und habe jetzt ein Problem. Eine meiner Applikationen lässt sich nicht mehr im Debugmodus starten, Noch vor dem Eintritt in die main()-Routine stürtzt die Applikation ab (siehe Screenshot im Anhang). Im Releasemodus läuft alles normal. Danke für Ihre Hilfe im vorraus. MFG, Christoph Pierednik.

[Wolfgang]

Hello Christoph,

there is no screen shot attached ...

If only the debug version is affected you might want to try deleting the debug information of this project, in the folder MeinProjekt\cvibuild.MeinProjekt\Debug

[snoop]

Here is the screenshot.

Deleting the Debug Information did not help. Also '´Mark project for compilation' did not help.

[HoussamK]

Hi

When debugging is enabled, LabWindows/CVI uses information it gathers from compiling your source code to make extensive run-time checks to protect your program. When it encounters a protection error at run-time, LabWindows/CVI displays a dialog and suspends execution.

You can use the SetBreakOnProtectionErrors function to prevent LabWindows/CVI from displaying the dialog and suspending execution when it encounters a protection error. In general, it is better not to disable the "break on protection errors" feature (Options»Run Options»Break on Library Errors). Nevertheless, you may want to disable it temporarily around a line of code for which LabWindows/CVI is erroneously reporting a protection error.

[HoussamK]

Hi

"FATAL RUN-TIME ERROR: Unknown source position, thread id ...: A non-debuggable thread caused a 'General Protection' fault at address..."

LabWindows™/CVI Programs Linking to Mixed-Mode DLLs Crash

[Wolfgang]

Hi hsm78,

according to the original post there was no error when run in CVI2009, the error started after upgrading to CVI2010SP1. The article you have linked seems to explain the opposite behavior...

Hello Christoph,

are you calling any low-level routines (see here)? 

[snoop]

I think I do not call any low level routines.

I receive the runtime error before calling any routine (before the main()-routine).

The other Problem is, that I can not find the displayed exception addres in my generated 'map'-File.

If it's a problem of mixed-Mode-DLL's, how can I find out which mixed-Mode-DLL causes the problem?

I do not link any DLL in my Project.

I guess, It must be a Windows or National Instrument DLL!?!?

[LuisG]

Can you verify whether other programs that you try to debug have the same problem? Let us know if you have the same problem when you run some of the CVI example programs.

If the example programs work okay, and you do not use any DLLs (there are no .lib or .fp files in your project, correct?) then I can't think of a good reason why the program would crash before entering main. At that point, if I were you, I'd make a copy of my project, and then, while using the copy, I'd starting taking away most of the code, gradually, until the crash no longer happened. If it continues happening even after you remove all the code, then it must be something in the workspace or project files, but we can look at those if and when you get to that point.

Luis

[LuisG]

There's one other thing you can do... after the program crashes, CVI should suspend the application and allow you to interact with the debugger. Granted, your program hasn't entered main() yet, but if you open the Modules window (Window>>Modules) you might be able to see, based on the address ranges, which module triggered your exception (0x0BD7E6DE).

Also, after re-reading your initial question it seems as if this is the only program that you can't run. So, if there are other programs that you can run, it would also be useful to find out what might be different between this one and the others.

Luis

[vix · Accepted solution]

In the past I had the same problem and thanks to NI support I solved it.

As explained here I had to remove some of the listed import library I had previously included.

As a matter of fact in the document I linked there is

The base version of LabWindows/CVI includes these import libraries, and LabWindows/CVI automatically loads these libraries when it starts up and searches them to resolve references at link time. Thus, you do not have to include these libraries in your project.