I have been unsuccessful at tracking down the source of an intermittent runtime error stating that a pure virtual function call has been made. This runtime error completely crashes the TestStand program. I believe this issue is similar to one reported to you previously,
please click here to view that article.
The following is a response to the questions you asked in that article:
1. What is happening when the error occurs?
TestStand is executing a call to a DLL method. However, the runtime error is never caused by the same method or DLL.
2. Does the error always occur in the same place?
No, sometimes a test sequence may run all day and other times it will fail after only an hour and report the runtime error. Furthermore, multiple DLL methods from different DLLs appear to cause the problem.
3. Does it always occur with use of certain resources (e.g. DAQ, GPIB, VISA, printer)?
The only consistency with this issue is that the runtime error occurs only on those steps where a DLL is being accessed. The DLL does not access anything aside from sockets on the local machine. (I have explored the socket calls as a possible source of the virtual function call error, but I was unable to find anything that would cause the error.)
4. Does it occur when using the sequence editor?
The sequences are executed using the seqedit.exe located within the bin directory for TestStand.
5. Does it occur when using one of the shipping operator interfaces?
We only use the basic user interface to open a sequence and execute a single pass of it.
6. Does it occur only when using your operator interfaces?
We do not use any custom interfaces.
7. Is it related to a specific sequence or any sequence?
No, it can happen in any sequence that calls a DLL.
8. Does it happen when you executed your sequence with/without a process model entry point (i.e. Execute>>Test UUTs, Execute>>Single Pass or Execute>>Run MainSequence)?
Single Pass � Has the worst performance, the runtime error occurs more frequently.
Run MainSequence � Has better performance than Single Pass, the runtime error occurs half has much.
Test UUTs � Has about the same performance as Single Pass.
9. How often does it happen?
Frequently � a sequence may execute successfully but fail with the runtime error when it is re-run. Or, it may fail on the first try and run successfully on the second.
10. What version of TestStand are you using?
3.0
11. With what language (include versions) are you programming your code modules?
The DLLs were developed using Borland C++ 5.0. (I have adjusted the byte boundaries to accommodate for this development environment.
12. With what language (include versions) are you programming your operator interface?
N/A
13. Is there any error code reported with this error message?
The error dialog states that the error occurred within TestStand and it gives a R60625 error code.
14. Is this error reported in a TS run-time error dialog or is it reported directly 1by the operating system?
It is reported directly by the operating system.
15. Have you searched the web for related errors?
Yes, I have researched this topic quite extensively. I have checked my source code for any possible instances where I made calls to pure virtual functions. But, as of yet, I have been unable to find anything wrong in my source code.
Please let me know if you require any additional information.
Thanks.
