LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Application Crash

I have a program that has been running for a few years that has crashed very sparingly.  It comes up with windows had to close the program error and gives you the address of the error.  I am running CVI 9.0 and running in debug mode.  My question is does Windows & Labwindows create the same memory map every single time?  So I would be able use the Generate map feature in the build options (I am now using this feature but it hasn't crashed yet) and run it again to find where that error resides?  If the program doesnt create the same memory map every time is there anyway to make this information useful?

thanks

0 Kudos
Message 1 of 3
(3,111 Views)

I had a similar experience some time ago and I managed to solve it exactly as you are doing: generating the map file and waiting for the error to raise: the address in the error message permitted me to locate the function on error so giving me useful informations as of where to investigate. I assumed the memory map would not change from execution to execution and infact the error was consistently raising in the same memory location. The program was running in release mode on a machine without the CVI IDE installed (only the runtime engine).



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 2 of 3
(3,097 Views)

Yes, this is correct. The memory map can change if you rebuild the program. But it won't change with multiple executions of the same executable.

 

Luis

0 Kudos
Message 3 of 3
(3,082 Views)