LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with XControl and remote debugging

Solved!
Go to solution

Can you make a remote debugging connection to an EXE or DLL that uses an XControl?  So far, my experiments would indicate the answer is no, but I find this surprising and have seen no previous mention of it in bug reports or in the forums.  When trying to connect to the DLL with XControl, I get a "Fatal error occurred during operation, closing connection" error dialog.  I am simply connecting from the local machine- not over the network.

 

My actual application is a rather elaborate DLL that is called from a Visual Studio 2008 C++ app and launches LV panels dynamically.  I realized that my DLLs that include panels with XControls are not allowing remote debugging to connect, while DLLs without XControls work fine.  This is the only difference between the two projects.

 

I simplified this to a very simple test program that simply updates one indicator in a timed loop.  I created two versions of the VI, one which updates a simple numeric, and another which updates an XControl (which itself is a simple numeric- only change from XControl template is dropping a numeric indicator onto the Facade FP and updating a local variable to it in the Data Change event).  I then built these two VIs into EXEs and tried to make a debugging connection to each after launching the EXE.  Sure enough, the app with the XControl gets the error dialog mentioned above.  Any ideas on why this is happening?

 

I've attached the sample project that builds the two EXEs.  One is called Test Debugging with XControl, and the other Test Debugging without XControl.  My LV ver. is 9.0f2.  Here is the very simple diagram demonstrating the problem:

 

17609i23796D055BA87DD3

0 Kudos
Message 1 of 9
(4,012 Views)

Hi Eric,

 

That is certainly strange behavior. I will need to check with our R&D department to see if that is expected.

Joe Daily
National Instruments
Applications Engineer

may the G be with you ....
0 Kudos
Message 2 of 9
(3,978 Views)

Hi Eric,

 

I spoke with R&D and this is definitely not expected and I have filed Corrective Action Request with R&D on this issue. If you have any questions or I can be of help please give me a call at 1.866.275.6964.

 

 

Joe Daily
National Instruments
Applications Engineer

may the G be with you ....
0 Kudos
Message 3 of 9
(3,962 Views)

OK, thanks Joe.  Just wanted to let you know that we (my client- Michael Christopher at ETS-Lindgren) and I filed a service request 7290443 yesterday with David.  I didn't want you guys to be duplicating effort.  Thanks for looking into this.

 

-Eric

0 Kudos
Message 4 of 9
(3,958 Views)

Hi Eric,

 

Thanks for letting me know, David and I were already working on the issue.

Joe Daily
National Instruments
Applications Engineer

may the G be with you ....
0 Kudos
Message 5 of 9
(3,954 Views)

 


@Joe D. wrote:

Hi Eric,

 

I spoke with R&D and this is definitely not expected and I have filed Corrective Action Request with R&D on this issue. If you have any questions or I can be of help please give me a call at 1.866.275.6964.

 

 


Can you post the CAR number?

 

0 Kudos
Message 6 of 9
(3,940 Views)

According to our reply from NI, the CAR number is 238566, and the projected LV ver for fix is 2010 SP1.  There are no known workarounds to the problem.

0 Kudos
Message 7 of 9
(3,927 Views)

 


@Eric Behrs wrote:

According to our reply from NI, the CAR number is 238566, and the projected LV ver for fix is 2010 SP1.  There are no known workarounds to the problem.


Thanks for letting us know the CAR number..Smiley Wink

 

0 Kudos
Message 8 of 9
(3,911 Views)
Solution
Accepted by topic author EricBehrs

I saw that this problem has been fixed in LV 2010 SP1:

 

http://zone.ni.com/devzone/cda/tut/p/id/12560

 

Search the CAR ID 238566 in the bug fix list.

 

0 Kudos
Message 9 of 9
(3,635 Views)