faulting module cvirte.dll

[JamesA]

I am using LabWindows 9.01 and I am having an issue with the program crashing. Following is pulled from the XP application event log.

(NOTE: This log entry occurrs at the time of the crash)

Faulting application bluetest.exe, version 1.0.0.0, faulting module cvirte.dll, version 9.0.1.375, fault address 0x0038e11a.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The crashes always occurr at fault address 0x0038e11a.

The following log entries occurr 1 to 7 times prior to the crash. There are several events of this type prior to the crash.

The description for Event ID ( 0 ) in Source ( CVI ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [22:15:04.250] [FATAL] [LRemoveItem] [..\james\list.c:543] Assertion failed: 0 (itemPosition >= kEndOfList && itemPosition <= (*theList)->numItems).

OR

The description for Event ID ( 0 ) in Source ( CVI ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [17:30:29.135] [FATAL] [LNumItems] [..\james\list.c:739] Assertion failed: 0 (CheckSanity(theList)).

What is the purpose of "list.c" and more specifically "CheckSanity(theList)" and "itemPosition >= kEndOfList && itemPosition <= (*theList)->numItems".

Thanks, Jim

[nickb · Accepted solution]

Hey Jim - 

I'm going to guess that you're running into the same issue reported here.  Are you also calling Delay() from threads other than the main UI thread?  If so, could you try replacing them with a call to Sleep() (#include windows.h)?

Thanks -

NickB

National Instruments 

[JamesA]

Thanks. Yes I am executing multiple threads. Switching from Delay() to Sleep() seems to have helped with the crashing. Is there any way for me to know what other LabWindows functions are safe (or not safe) for a multi-thread environment?

[nickb]

Hey Jim - 

Unless indicated explicitly in the function documentation for a particular function, we intend all CVI library functions to be thread safe.  In the particular case of Delay, a bug existed that rendered the function unsafe for multi threaded applications, leading to the crash you had seen.  This has since been fixed.

NickB

National Instruments 

[JamesA]

Thank you for your support. When will the update be available and where can I find it?

Thanks, Jim

[LuisG]

Hi Jim,

This was fixed in version the 2009 version that was just released. (Bug ID: 184428)

Luis

[JamesA]

Sorry I failed to mention. Delay() was working without crashing when I was using the LabWindows compiler version 8.1. It was only after upgrading to the 2009 Labwindows 9.0 that I started having problems with crashing. As soon as I replaced Delay() with Sleep() under LabWindows 9.0 the crashing has so far not happened, but the issue was infrequent and random so I have more testing to do to be sure.

Is there an update to the 9.0 release of 2009 LabWindows? 

Thanks, Jim A.

[LuisG]

Yes, this bug had been introduced in version 9.0 and it was only fixed in 2009.

LabWindows/CVI 2009 is a standalone upgrade. It is not a patch:

... 8.5 --> 8.5.1 --> 9.0 --> 9.0.1 --> 2009