Hello,
I'm using CVI 5.5.1 under Windows-NT & 2000. My applications are using DLLs written by another collegue, I link the DLLs dynamically.
I understand that Win-NT/2000 uses a MMU (memory management unit) to survey user applications not to violate protected memory.
As no software is error-free, things like stray pointers or out-of-bound array indices from time to time cause memory errors and bring the Dr. Watson analysis tool into action. In this case I observe 3 things to happen:
1) The CVI application is halted and a Dr. Watson message window appears telling e.g. "Memory Access Violation"
2) When closing the message window, Dr. Watson writes a fingerp
rint of the faulty situation into a logfile
3) My CVI application is terminated without giving me any chance to e.g. write own fingerprints into my own trace file.
Question:
Does anyone know how to embed into a CVI application a callback function (a kind of software watchdog). Instead of engaging the brutal Dr. Watson, the MMU should be ordered to call back my own CVI watchdog service giving me a chance to close my application myself .
The 1st advantage would be that I could write trace file info in terms of MY mnemonic naming instead of finding not understandable disassembler trace info in the Dr Watson log file.
The 2nd advantage would be that I could close the tracefile and preserve other things before ending my CVI applicatiom.
The 3rd advantage would be to avoid quarreling with the collegue whether his DLL or my EXE have origined the memory protection fault. - My trace file would show it.
Heinz
