Remote Debugger Fails to Connect

[tyk007]

I am attempting to connect to a Labview built executable (in LV2011, no SP) on the same computer ie. localhost. The exe has debugging enabled and appears in the remote debugging list.

Once connected (the executable shows the connected message), the debug downloads all the VI content, but near the end generates a "Fatal error occurred during operation, closing connection".

Multiple attempts produce the same error message.

Any thoughts? Am trying to debug why the build executable executes differently than the development environment and this appears to be the only real trouble-shooting method.

[SunainaK]

Hi tyk007,

Just to make sure everything is set up correctly I have attached a document below which walks through all the steps of setting up remote debugging:

http://digital.ni.com/public.nsf/allkb/8DA679805915DE40862572D5007B2F70

[tyk007]

Hi there, sorry for the late reply.

I followed all the instructions you listed. The debugger will now connect, but once control has been transferred the entire user interface becomes non-responsive (just multiple "Control transferred" messages floating over the interface. The mouse pointer will change as I move over buttons, controls etc. but I am unable to interact with the interface any longer. I figured this was normal behaviour; however moving to the LabVIEW environment and clicking on the [Remote Debugging] VI window does not open the wndow - clicking on this icon in the task-bar apparently does nothing. Perhaps there is some setting for the VI Front Panel that is important to allow correct debugging? My VI's do not have a title bar, menu bar or tool bar(s) (customer request) so there is no other interaction available to me.

Thanks for your help.

Edit: disconnecting the debug session via Quit Debug Session and attempting to close the build application results in a LabVIEW internal error. My company security policy appears to prohibit me from performing any uploading but it appears to be an Access violation error (0xC0000005) at EIP=0x6300011.

---

@SunainaK wrote:

Hi tyk007,

Just to make sure everything is set up correctly I have attached a document below which walks through all the steps of setting up remote debugging:

http://digital.ni.com/public.nsf/allkb/8DA679805915DE40862572D5007B2F70

---

[SunainaK]

Hi tyk007,

On the document:

http://digital.ni.com/public.nsf/allkb/8DA679805915DE40862572D5007B2F70

under step 2 it appears as though you may have checked the Wait for debugger on launch. If you check this the executable will launch but not run.

[tyk007]

Hi there,

Sorry, I should have clarified - the first VI opens and allows me to run via the toolbar. This first VI is basically a splash screen. When I run this VI (which works correctly), it opens another VI which is the main UI VI. This VI contains SubPanels that load other VIs in based on operator selection (menu). It is this last main UI VI that appears "locked up".

If I do not check the "Wait for debugger on launch" option then I have the same error as I posted in my original post (debugger connection fails during download of the VIs).

Any other ideas?

Thanks.

[Cole_R]

Hi tyk007,

Is the executable capable of getting passed the point that it appears 'locked up' if the Remote Debugger is not connected?  Is the application actually frozen or is the execution just really slow?  It sounds as though you may be running into limitations with your computer.

[tyk007]

Hi Cole,

I am running the application on a quad-core Xeon processor, with each core running @ 3.3GHz. It is a Windows 7 system with 8GB RAM. It can run the build without debugging utilising around 0.5% to 1.5% CPU maximum (according to the Windows Performance Counters) running over several hours.

My application is relatively small so this computer is clearly overkill  .I would have thought it unlikely that using the remote debugger gives such a performance hit but yes, as I stated in my earlier post if I dis-connect the remote debugger the application will continue to run just fine but generate a Labview Internal Error on exiting.

I have made a small test application (a single VI with a loop and Stop control), built it, the remote debugger appears to connect ok etc.

The only non-Labview feature in my application is the use of .Net assemblies. My project makes use of three such assemblies - two directly from the Framework (in the System namespace) and one from a custom dll.

Any other thoughts?

[Cole_R]

Hi tyk007,

Is it possible that you could post your code so we can test it out?  Or if not, are there any error codes or screenshots that may be helpful?