tscvirun error

[hurst]

When I run Test sequences from the sequence editor, I get the following error in tscvirun:

" HEAP[tscvirun_dbg.exe]: Invalid Address specified to RtlFreeHeap( 850000, 1d51cc8 )"

How do I correct this problem ?

[Matt Pickard]

Hurst,

To get around that problem, you can change your CVI Adapter configuration in the Sequence Editor (Configure >> Adapters, then select the Labwindows/CVI Adapter and select Configure)'Execute Steps In-Process'. This option doesn't use the tscvirun.prj. If you need to debug CVI DLL code from TestStand, then you can simply launch the sequence editor from the CVI environment (Run >> Specify External Process..., then just browse to the sequence editor). After you go through the previous process, you should see the green Start button in CVI become active. When you run your CVI project it will launch the Sequence Editor, which you can use in the same manner as if you launched it from the start menu. Any breakpoints you set in CVI will be honored when you
run your TestStand sequences.

Best Regards,

Matt P.
Applications Engineer
National Instruments

[Scott_Richardson]

Hurst -
I assume that you are seeing this "error" in the debug trace of LabWindows/CVI. This typically occurs for one of two reasons.
1) You are calling the incorrect free function for allocated memory.
2) You call the correct free function, but the pointer gets value is corrupted.
If you are using the standard CVI prototype from TestStand 2.x, and you attempt to reallocate a string in the tTestData or tTestError structures, make sure you use the free and malloc pointers that are stored within the struct.

Do you know when the debug message appears, i.e. a specific line in your code?

Scott Richardson (NI)

[hurst]

This worked great!

[hurst]

Matt Pickard already provided an answer that works. I believe the problem lies within the tscvirun ActiveX Automation Server since that is where the error is reported.

[Scott_Richardson]

To Hurst -
If you assume that the memory warning is caused by the tscvirun project code then going to the inprocess mode for the CVI adapter would fix the problem. But, if there is a bug in the code module code, the problem will not be fixed by going to the inprocess mode. The best thing to do is to single step thru your code to determine whether the warning is being raised by some call to function that frees memory in your code.

Scott Richardson (NI)