debugging error in CVI from within TestStand, crashes entire TestStand app

[rjohnson]

okay, maybe it's not technically a "crash" but the end result is the same.   Here's the scenario:

I'm debugging a DLL created by CVI within TestStand.

the DLL has a runtime error that needs to be debugged, so I BREAK and launch CVI debugger.

eventually the CVI Debugger needs to be terminated (say for a Fatal Error), and a popup says "This will terminate the process being debugged.  Do you want to terminate that process?"

One would assume that CVI is the process to be terminated, right?  well, apparently not, because if I say "Yes" it forces an immediate shutdown of TestStand and leaves the terminated DLL open in CVI.   which isnt much use, so i shut that down too, and reopen TestStand.   which is becoming quite annoying.

any suggestions or hints on how to stop this behavior from occuring?

[John_P1 · Accepted solution]

Hi rjohnson,

Are you following the recommended process for debugging your dll?  Any details about the exact steps taken to reproduce the behavior might be helpful, but I would first make sure that you are following the steps linked in the KnowledgeBase.

One thing to note is that TestStand itself utilizes the CVI runtime engine, so if we are terminating the CVI Debugger I could understand why it might shut down TestStand (although it's understandable that this could be rather annoying).  In any regard, if you let me know more details about the steps you are taking I can look into the matter a bit further.

Best Regards,

John

[rjohnson]

you're right.   i was executing the dll "in-process".   changing it to external instance has solved that problem.

and i'm reminded once again about using the word "crash" sparingly...   🙂

thanks