cvi teststand debug not working

[JMH]

CVI 7.1.0
TestStand 3.0
application: TestExec

I have been compiling and debugging without any problem, but suddenly I can't debug my testexe. I can debug other apps and if I move my project to another machine I can debug there (although it is running CVI 7.0 and Testand 3.0).

After compiling and linking I press Shift+F5 and CVI acts as if it is going to bring up testexec but it then disappears completely. I have tried setting break on first statement but it never gets there.If I execute the exe with Ctrl+F5 it runs fine. I have noticed that there is data in the debug output window, it is difficult to copy it all because it scrolls so fast but I managed to copy the following. This listing was long so I have omitted some lines.

[ff0,1c0] LDR: Real INIT LIST for process c:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\User\Full-Featured\CVI\TestExec.exe pid 4080 0xff0
... lines omitted...
NAME - InitializeCriticalSectionAndSpinCount
[ff0,1c0] LDR: WINSPOOL.DRV loaded - Calling init routine at 73004D00
[ff0,1c0] LDR: SHLWAPI.dll loaded - Calling init routine at 77F651FB
NAME - CreateTimerQueue
... lines omitted...
[ff0,1c0] LDR: COMCTL32.dll loaded - Calling init routine at 5D0932DA
NAME - InitializeCriticalSectionAndSpinCount
... lines omitted...
[ff0,1c0] LDR: SHELL32.dll loaded - Calling init routine at 7C9E7376
... lines omitted...
[ff0,1c0] LDR: Real INIT LIST for process c:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\User\Full-Featured\CVI\TestExec.exe pid 4080 0xff0
[ff0,1c0] C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll init routine 773D42B3
[ff0,1c0] LDR: comctl32.dll loaded - Calling init routine at 773D42B3
... lines omitted...
[ff0,1c0] LDR: comdlg32.dll loaded - Calling init routine at 763B1AB8
[ff0,1c0] LDR: ole32.dll loaded - Calling init routine at 774FD0A1
[ff0,1c0] LDR: OLEAUT32.dll loaded - Calling init routine at 77121558
[ff0,1c0] LDR: cvirte.dll loaded - Calling init routine at 685E0BA8
... lines omitted...
f0,1c0] LDR: Real INIT LIST for process c:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\User\Full-Featured\CVI\TestExec.exe pid 4080 0xff0
[ff0,1c0] C:\WINDOWS\system32\psapi.dll init routine 76BF10F1
[ff0,1c0] LDR: psapi.dll loaded - Calling init routine at 76BF10F1
NAME - EnumProcesses
NAME - EnumProcessModules
NAME - GetModuleFileNameExA
[ff0,1c0] LDR: Real INIT LIST for process c:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\User\Full-Featured\CVI\TestExec.exe pid 4080 0xff0
(1) [cvi.DLL] C:\Program Files\National Instruments\CVI71\cvi.DLL (0) deinit 0
(1) [psapi.dll] C:\WINDOWS\system32\psapi.dll (0) deinit 76bf10f1
[ff0,1c0] LDR: Real INIT LIST for process c:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\User\Full-Featured\CVI\TestExec.exe pid 4080 0xff0
[ff0,1c0] C:\WINDOWS\system32\uxtheme.dll init routine 5AD71626
[ff0,1c0] LDR: uxtheme.dll loaded - Calling init routine at 5AD71626
[ff0,1c0] LDR: Real INIT LIST for process c:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\User\Full-Featured\CVI\TestExec.exe pid 4080 0xff0
[ff0,1c0] C:\WINDOWS\system32\MSCTF.dll init routine 747213A5
[ff0,1c0] LDR: MSCTF.dll loaded - Calling init routine at 747213A5
NAME - NtQueryInformationProcess
NAME - CtfImmCoUninitialize
NAME - CtfImmLastEnabledWndDestroy
NAME - CtfImmSetCiceroStartInThread
NAME - CtfImmIsCiceroStartedInThread
NAME - CtfImmIsCiceroEnabled
NAME - CtfImmIsTextFrameServiceDisabled
NAME - CtfImmEnterCoInitCountSkipMode
NAME - CtfImmLeaveCoInitCountSkipMode
NAME - ImmGetDefaultIMEWnd
NAME - ImmReleaseContext
NAME - ImmNotifyIME
NAME - ImmSetConversionStatus
NAME - ImmGetConversionStatus
NAME - ImmGetProperty
NAME - ImmGetOpenStatus
NAME - ImmGetContext
NAME - ImmSetOpenStatus
NAME - ImmInstallIMEA
NAME - ImmGetDescriptionA
NAME - ImmGetDescriptionW
NAME - ImmGetIMEFileNameA
NAME - ImmGetIMEFileNameW
NAME - ImmSetHotKey
NAME - GetUserDefaultUILanguage
NAME - GetClipboardSequenceNumber
NAME - GetSystemMetrics
NAME - MonitorFromWindow
NAME - MonitorFromRect
NAME - MonitorFromPoint
NAME - EnumDisplayMonitors
NAME - GetMonitorInfoA
NAME - EnumDisplayDevicesA
NAME - MsgWaitForMultipleObjectsEx
NAME - VirtualProtect
NAME - VirtualQuery
NAME - __CreatePtrInfoForCommandLine
NAME - malloc
NAME - VirtualProtect
NAME - VirtualQuery

[Travis_M.]

Hello,

I'm not real familiar with TestStand, so forgive me if this sounds like a bad question.  However, are you having problems just running and debugging your program in the CVI platform?  i.e. if you open you CVI program from CVI can you run and set breakpoints, and other debugging things from here?  If its not this, the problem probably lies somewhere in the TestStand interface with CVI and the question might be better off in the TestStand discussion form threads.

If this is an issue you believe is related to the CVI environment please let me know how I can help!

[JMH]

Hi Travis,
Yes, I am having problems debugging just my teststand enabled app. (testexec). I can debug my not teststand apps. without problem. I posted here because of the debug output in CVI. I assumed that this is generated by the CVI debugger and a developer would see it and immediately know what kinds of situations would force CVI into such verbose debug output.

Let me know if you think I should post this to the Teststand forum.

Thanks,
John Hopkins
MTI

---

@Travis M. wrote:

Hello,



I'm not real familiar with TestStand, so forgive me if this sounds like a bad
question.  However, are you having problems just running and debugging
your program in the CVI platform?  i.e. if you open you CVI program from
CVI can you run and set breakpoints, and other debugging things from
here?  If its not this, the problem probably lies somewhere in the
TestStand interface with CVI and the question might be better off in the TestStand discussion form
threads.



If this is an issue you believe is related to the CVI environment please let me
know how I can help!

---

[TerryS]

Hi John,

Try creating a simple sequence that just shows a message pop-up and see if that works.  You could also try running your current sequence in the simple user interface.  It is located at: C:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\NI\Simple\CVI.  Try both of these out to see if there is an error occurring in the testexec.exe or if there is something in the sequence we need to take a look at.

[JMH]

Hi Terry,
I believe it has nothing to do with the sequence file as I never get to see the UI or run anything. I did try what you suggested, I brought up the testexec with Ctrl+F5 and closed the sequence file so the next time I debugged with F5 there would be no question of Testexec trying to load the sequence file and I still had the same problem.

Thanks,
John Hopkins
MTI

---

@tesims wrote:

Hi John,

Try creating a simple sequence that just shows a message
pop-up and see if that works.  You could
also try running your current sequence in the simple user interface.  It is located at: C:\Program Files\National
Instruments\TestStand 3.0\OperatorInterfaces\NI\Simple\CVI.  Try both of these out to see if there is an error
occurring in the testexec.exe or if there is something in the sequence we need
to take a look at.

---

[TerryS]

Hi John,

I’m a little confused.  Did you try running the simple CVI operator interface and it didn’t work, also?  Try running your sequence in a different operator interface, either the simple CVI one or the LabVIEW one.  If it works in either of those, then we need to take a look at the full CVI operator interface, to see where in the code it is crashing.

Here’s the path to the other operator interfaces:

C:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\NI\Simple\CVI\TestExec.exe

C:\Program Files\National Instruments\TestStand 3.5\OperatorInterfaces\NI\Full-Featured\LabVIEW\TestExec.exe

[JMH]

Terry,
I tried loading, compiling and debugging
C:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\NI\Simple\CVI\testexec.cws

I had the same problem as I did with my testexec project. Your links pointed me to exes, I have no problem running just the exes (compiled in Debug) outside of CVI or in CVI using Ctl+F5 (execute ). To be clear I can load my testexec or the simple testexec project and press Ctrl+F5 and they will both run fine; however if I press Shift+F5 to debug they both crash with the output I posted earlier. I believe this has nothing to do with sequences.

Thanks,
John

---

@tesims wrote:

Hi John,

I’m a little confused. 
Did you try running the simple CVI operator interface and it didn’t
work, also?  Try running your sequence in
a different operator interface, either the simple CVI one or the LabVIEW
one.  If it works in either of those,
then we need to take a look at the full CVI operator interface, to see where in
the code it is crashing.

Here’s the path to the other operator interfaces:

C:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\NI\Simple\CVI\TestExec.exe

C:\Program Files\National Instruments\TestStand
3.5\OperatorInterfaces\NI\Full-Featured\LabVIEW\TestExec.exe

---

[TerryS]

Hi John,

If you create a simple sequence that just shows a MessagePopup, does it crash in debug mode also?

[JMH]

Terry,
I think we are miscommunicating. I don't load or execute any sequence files. I brought up the testexec (both mine and the simple one) using Ctrl+F5 and made sure no sequence file was loaded to avoid the autoload process. I then compiled both testexecs and pressed Shift+F5. The process does not proceed far enough in debug mode for me to see or interact with with a UI.

Although I did as you asked I ran my testexec and the simple one (both compiled in Debug) using Ctrl+F5 (execute) and they both run benchmarks.seq without problem.

Thanks,
John

[RayFarmer]

Hi,

Have you tried deleting the cvibuild.Testexec folder, the cdb and the exe and tried to do a fresh build.

Or even make a fresh copy from the NI folder to User folder.

Regards

Ray Farmer