I periodically get an error in my test programs that I have running TestStand 3.1f1 and LabWindows 7.1.1. The error message is a LabWindows/CVI Message "A non-debuggable thread is trying to suspend execution at address 00000001. Do you want to suspend execution?" If I click Yes is pauses the CVI execution, if I click no the program goes on apparently without problems. While it happens randomly in my test program, I have found a way to reliably reproduce this same error popup. I have created a CVI DLL, in this case I called it Error00000001.dll, and added the DllMain and a function EditTestStep. EditTestStep takes no parameters and just returns a double 3.0. I then specified SeqEdit.exe as my external debug process. In TestStand I created a sequence that has a custom step. The custom step was one I just created in the Type Palette editor. I added my step then edited the properties and added a substep "Edit" which was in the list of substeps to add. I specified my CVI DLL as the module for this substep and had it call my EditTestStep function. Ok, now if I execute SeqEdit.exe from CVI as my debug executable it will bring up my sequence which only has the custom step I just created in it. If I right click on that step and select "Edit" I will get the 00000001 error in CVI before it gets to the DllMain or EditTestStep function in my CVI DLL. I have to do this twice, IE the first time I load TestStand from CVI and click the edit it will work fine, I then exit TestStand and rerun the debugger from CVI and do the same thing and I get the error. Now I know this is somewhat convoluted, but it is so far the only reliable example I have been able to generate to display this error.

LabWindows/CVI

Hey Todd,

The patch is now available on the web LabWindows/CVI Version 7.1 for Windows 2000/NT/XP -- Patch. Please email NI support if this does not resolve your issue.

Have a great day,

Ecleamus R.

Message 11 of 11

(772 Views)