NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Heisenbug: Subsequence call, different file, LabVIEW

Actually LabVIEW does start -- but it conks in my initialization code with a fairly deep call stack.

 

Putting together a small (and non-proprietary) example is not simple. Will work on it some more.

 

- Steve.

 

0 Kudos
Message 11 of 25
(1,967 Views)

Hi,

 

Is this running on a deployed system using an UI or in the SeqEditor?

 

Regards

Ray Farmer

Regards
Ray Farmer
0 Kudos
Message 12 of 25
(1,965 Views)

In the Seq Editor.

 

- Steve.

0 Kudos
Message 13 of 25
(1,961 Views)

Hi,

 

Looking at your attached rtf file, you need to make sure any references you spawn off the Reference you pass to the code module must be released/closed before you return back to TestStand.

eg If you pass SequenceContext into your code module and you create an Engine reference by using SequenceContext.Engine and then create a Globals reference, you must make sure you close the Globals reference and the Engine reference after you have finished with them and before you exit the code module. You dont need to close the SequenceContext as TestStand will release that.

 

Look at Using LabVIEW with TestStand Appendix C - 6 for an example

 

Regards

Ray Farmer

Regards
Ray Farmer
0 Kudos
Message 14 of 25
(1,961 Views)

Hi, Ray,

 

The conk happens before LV returns to TestStand from the first call.

 

- Steve.

 

0 Kudos
Message 15 of 25
(1,959 Views)

Hi Steve,

 

So what are you doing in this first LabVIEW call. Are you talking to any hardware?

 

Regards

Ray

Regards
Ray Farmer
0 Kudos
Message 16 of 25
(1,948 Views)

Hi, Ray,

 

Not at that time. I'm building a fairly complicated LVOOP object structure as part of the hardware configuration. 

 

BTW, I've submitted the problem to NI. I still haven't figured out how to cut down the crash to something that would be disclosable on a public forum. But I've made progress, and I'll keep trying.

 

- Steve.

 

0 Kudos
Message 17 of 25
(1,935 Views)

Hi Steve,

 

Can you step into the LabVIEW code and identify a point just before it crashes?

 

Regards

Ray

Regards
Ray Farmer
0 Kudos
Message 18 of 25
(1,932 Views)

Hi, Ray,

 

Have done so. It crashes just when it tries to invoke a method to configure a certain newly created sub-object. I can't even take a breakpoint at the start of the configure VI; the crash happens before it even starts.

 

No rhyme or reason to it; the code works fine elsewhere and under other conditions.

 

- Steve.

 

0 Kudos
Message 19 of 25
(1,930 Views)

HI Steve,

 

So if you take it out or not create the object does it not crash?

 

Regards

Ray

Regards
Ray Farmer
0 Kudos
Message 20 of 25
(1,906 Views)