Sometimes we have a problem about Teststand's sudden shutdown. one case is everytime when I execute TestUUT, Teststand will be automatically shut down, even I reinstall Teststand. My questions are:
1, Why Teststand will automatically shut down
2, Under what kinds of conditions Teststand will automatically shut down
3, How to quickly fIND the root cause? Is there any tool/method to find out what has cause the problem?
4, sometimes, the root cause lies in the called module, such as DLL, so what's the suggestion during the development of modules, in order to reduce the occurrence of Teststand shut down?
Thanks a lot!
The only way TestStand is going to shut down automatically, is you have programmed it too, either in your IO, or by way of the command line argument /quit.
If you haven't done any of these, then its due to a code module, probably corrupting memory.
One way to locate it, is by stepping through your sequences. If your sequences are rather large, then you could place a breakpoint half way. If it hasn't crashed before you got to the breakpoint. then place the next breakpoint, halfway in the remaining steps, and so on, until you get to the point where it crashes.
Alternatively, if you can identify roughly where in the sequence of step the crash occurs, you could narrow down your placement of the first breakpoint.
If it is in a DLL, then you can run in debug mode from your IDE (such as CVI) and specfiy the SeqEditor.exe as the External Process so that you can step it too your DLL code modules.
Hope this is of some help to you.