LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

CVI 8.5 IDE fatal errors

I may have been generating a control callback prototype from the UIR panel or viewing a control callback. (I remember the reason I switch to the UIR was to navigate the callback for one of the controls) The target file may or may not have been set, but not be me, to the incorrect file like it was when I recovered from the crash.  I will try to pay closer attention next time... it's not the sort of thing I commit to memory in detail. 🙂

I was not generating a function panel from an include file specifically, but I do have function panels included in the project, one was generated by the wizards from an activeX control, though I think that might be stretching the limits of your question.


Greg

 

0 Kudos
Message 11 of 64
(3,011 Views)
Got another one... wasn't really doing anything this time.. just sitting in a source window readying code..  001B:103C9FF7.  This time with a clean shutdown (no other errors).
Greg
0 Kudos
Message 12 of 64
(3,010 Views)
Okay, try disabling auto-backup (Options>>Environment>>Enable auto backup) and run for a few days with it disabled to see if it makes a difference. Since you mentioned that you were just looking at some code -- you weren't even interacting with CVI at the time -- it makes me suspect this feature. And there is in fact a known issue in CVI 8.5 where auto-backup can cause a crash when it backs up the file, in some conditions.
 
It's only a shot in the dark at this point, but it's worth a try.
 
Luis
0 Kudos
Message 13 of 64
(3,003 Views)
Auto backup was already off. Auto save workspace was on. (now off). 
0 Kudos
Message 14 of 64
(2,984 Views)
Well... then I'm not sure what it could be. Based on the memory address, the last one that you reported might have been related to the collapsible regions (which you can also disable) but if so, that's not a known issue at this point.
 
Until we know of some sequence of actions that reproduces the problem (even if it's not every time) we're going to be pretty limited in trying to figure out what's happening. The only I thing I can ask you and menchar to do is that whenever you do see a crash, that you post here the memory address that the popup displays, as well as some brief description of what you were doing at the time. Given a few more of those, we might be able to establish a pattern and then narrow down the problem.
 
Sorry for the hassle...
 
Luis
0 Kudos
Message 15 of 64
(2,971 Views)

Addr: 001B:1060E6D6

Action: Opening CVI/Loading recent workspace. (I don't remember if I got past the splash screen to select a recent project or not)



Message Edited by gvan on 02-12-2008 01:56 PM
0 Kudos
Message 16 of 64
(2,961 Views)
And it only happened once? When you restarted CVI afterwards and opened that same workspace, it didn't happen?
0 Kudos
Message 17 of 64
(2,943 Views)
That is correct, just once, then not again.  If I could repeat any of these with a set of known events I'd let you know.
0 Kudos
Message 18 of 64
(2,939 Views)
Actually I've gotten a crash a few times now as well, although taking a different route.  The most recent one:


1. Hit the run arrow
2. Message pops up about it being in release, do you want to run debug
3. Hit cancel
4. Manually change it to debug mode... build->configuration->debug
  --- crash here: Internal Error 001b:101cdf7b
0 Kudos
Message 19 of 64
(2,932 Views)

001B:100EF866

Building an application, at least one file needed to be saved.  The "save changes to <file>?" box was behind (or came up afterward) the fatal error box when I clicked [ok].

 

 

0 Kudos
Message 20 of 64
(2,907 Views)