LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

General protection fault after installing CVI 2010

I just installed CVI 2010 on my PC, which already had CVI 2009 SP1 installed on it.  After installing CVI 2010, I now get a general proctection fault when exiting my application when running it through the debugger.  The specific message is:

 

FATAL RUN-TIME ERROR:  Unknown source position, thread id 0x000011F8:  The program has caused a 'General Protection' fault at 0x68449F0A

 

Note that thread id does change, but the address of the general protection fault is always the same.  This happens after the main function returns.

 

I get this error in CVI 2010 as well as CVI 2009 SP1 now, even when running a copy of the project in CVI 2009 SP1 from before I installed CVI 2010.  This suggests to me that some shared library or driver got changed when CVI 2010 was installed that is affecting both copies of CVI in some bad manner.  The PC is running Windows XP SP3.  Any ideas?  Thanks.

0 Kudos
Message 1 of 5
(3,716 Views)

Hey tstanley -

 

Could you please follow the instructions here to generate a crash dump I could take a look at?  Once you've posted it to our ftp site, I'll take a look.

 

Thanks -

 

NickB

National Instruments

0 Kudos
Message 2 of 5
(3,709 Views)

Thanks for the reply.  If I try the steps in your link, curiously the application does not crash - it seems to exit cleanly when I close it after running it by double-clicking the debuggable .exe with CVI not open.  I tried a debuggable executable built with both CVI 2009 SP1 and CVI 2010.  I also tried a release executable too.

0 Kudos
Message 3 of 5
(3,705 Views)

Shucks... Things become a little trickier to debug if I can't get a crash dump.  A couple questions:

 

  1. Does this happen for many different projects? (ie, any of our examples?)
  2. If it does not happen with our examples, is there any chance I could get your code to try to reproduce the issue here (it would need to exclude any hardware calls etc.)?

If the answer is no to both of these questions, we will likely need to send you debug versions of the runtime with some logging added to them.  If this is the case, I will send you a private message requesting some more information.

 

Thanks -

 

NickB

National Instruments

 

0 Kudos
Message 4 of 5
(3,674 Views)

Hi,

 

It only happens on one of our large projects.  I played around with it, stripping things down to the point where it finally went away.  I managed to figure out the source of the error, it appears that there was an old copy of a NI DLL called "instrsup.dll" in the project directory.  If I delete the file then the problem goes away.  Presumably it then goes to the copy in the Windows System32 directory that appears to have been updated with the CVI 2010 installer (the copy in the project directory was from Feb. 2005).  I'm guessing that instrsup.dll is part of the CVI runtime engine?

 

I put a sample project in the FTP called "2010_Test.zip" in the NI FTP incoming folder if you still want to take a look at it, but I think I have a pretty good handle on what's going on, or at least how to fix it.

 

Thanks for your help!

0 Kudos
Message 5 of 5
(3,668 Views)