LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Unrecoverable Internal Error @ 001B:109A4917

Hey Nick,

   Here is my first DeBug enabled CVI crash that I got a .dmp file... attached the .log and the .dmp in a zip and will try sending this to ya... if the server complains then I will attempt to ftp the file...

 

Regards,

ChipB

Message Edited by ASIC IIBU Tech on 04-09-2009 02:12 PM
0 Kudos
Message 21 of 33
(2,366 Views)

Hey Chip,

 

This is very strange.  For some reason neither Visual Studio nor WinDbg can make use of that dump file.  Are you using Windows XP?  Can you post the dump for your next crash in case this was just a random data corruption?

 

Thanks,

 

NickB

National Instruments 

0 Kudos
Message 22 of 33
(2,362 Views)

Nick, 

Windows XP and Ok... I am waiting for my next dump...Smiley Happy

 

ChipB

0 Kudos
Message 23 of 33
(2,356 Views)

Nick

I have to create an account to ftp data... the requirements are a contact (you) and a IP address... so all I can do for now is attach the .zip files,

 

ChipB

cbuchanan@ti.com

0 Kudos
Message 24 of 33
(2,318 Views)

Hey Chip,

 

Thanks for the latest information. Upon looking at the .dmp, we think the issue you are seeing may be an issue we have identified in CVI 9.0 and have fixed for the upcoming maintenance release.  Do you have any particularly large strings that you are initializing to some small string in your code? eg:

 

 

char string[500000] = "";

 

 

 If not, I think we may be able to speed things along a little bit if I can contact you offline.  Do I have your permission to get your email address from the forum administrator?

 

Thanks!

 

NickB

National Instruments  

0 Kudos
Message 25 of 33
(2,299 Views)

Sure Nick,

   you have my permission and can e-mail me directlly. The max character array is 100000.

0 Kudos
Message 26 of 33
(2,285 Views)

Hey Chip, 

 

That char array may just be large enough to create the crash.  The only current workaround is to not initialize the string to some very small string.  I will contact you with more information once I get your email address.

 

NickB

National Instruments  

0 Kudos
Message 27 of 33
(2,269 Views)

Just a small correction to my previous post.  After talking with a colleague, It turns out that you should be able to initialize the string as follows: 

 

// use the following instead of: char string[100000] = "";
char string[100000] = {0};

 

Sorry for the inconvenience,

 

NickB

National Instruments  

0 Kudos
Message 28 of 33
(2,263 Views)

Hi Nick,

   So the code init's the variables like this...

#define MAXCHARREAD 100000

...

short CVICALLBACK readsweepdata (...)

{

char dataread[MAXCHARREAD] = "";

...

}

 

so if that string is initialized as a empty string array, would this not crash?

 

ChipB

 

 

0 Kudos
Message 29 of 33
(2,261 Views)

Chip - 

 

That's correct.  If the crash you are seeing is the same one as I suspect, initializing it as I mentioned directly above should keep the app from crashing.  Let me know if that turns out to not be the case.

 

NickB

National Instruments  

0 Kudos
Message 30 of 33
(2,259 Views)