Hello CviUser2003,
From the explanation of the problem in your previous posts:
When executing a DEBUG release of my application from the IDE, a message popup appeared indicating "Unable to allocate system resource". After pressing yes, it continued with my application, but in crippled version (other weird errors occurred).
I don't know if it is caused by my application's inefficiencies taking up so much memory? I upgraded to CVI 8.5.1 because my applications would not link under CVI 6 - gives an out-of-memory error. Until recently, CVI 8.5.1 did not give me any compile/link problems - I get an "Unrecoverable Error" (or something like that) inconsistently (during debug) which forces a closure of CVI. Restarting CVI allows me to continue.
You may want to debug your program to see if you are ever over-writing memory locations that you haven't properly allocated for use in your program. When I've come across programs/executables that display behavior similar to what you're experiencing, it's been caused by writing to non-allocated memory locations. Here is an example of a situation where it's possible to overwrite to non-allocated memory:
If you declare a character array of 8 elements called myCharArray, you've allocated 8 bytes of memory for myCharArray. Now, if you set myCharArray as the Target String input and a user input defined at run-time as the Source(s) input of the sprintf() function, if the user input defined at run-time is a string with more than 8 characters (for example "Hello World" is a string of 11 characters), then the sprintf() function is going to try to write "Hello World" to the myCharArray target string. It will write H-e-l-l-o- -W-o to the elements of myCharArray and then continue to write r-l-d to the next three memory locations. These next three memory locations were not specifically allocated for use in the program so they might be memory locations containing pointers or some other kind of information used by CVI or they might just be un-used memory locations.
This is why you may experience this behavior inconsistently. You may not be using the sprintf() function in your program but there might be certain parts of the code that use pointers and for loops to index through memory locations with those pointers. Try debugging your source code and see if this might be happening in your program.
Manooch H.
National Instruments
