03-08-2013 07:45 AM
I have tried to debug my application remotely. I managed to do that, but when i try to use probe on a block diagram application crashes.
I developed application with LabView 2012, I build it with Application Builder and I deployed it on a computer with Windows XP.
Breakpoints work fine. When i use probe I get access violation exception.
I tried to find something on Developer Zone, but unsuccesful.
03-14-2013 07:20 AM - edited 03-14-2013 07:21 AM
Hi and welcome to NI Forums!
I've tested the issue on a similar setup, but for me everything worked fine. Let me ask a few things to clarify the situation.
How are you connected to the remote computer? Are you on the same subnet?
What is the operating system on the Development Computer?
What type of wire are you probing when the crash happens?
How big is the application and how much resources does it use on the remote PC?
I'd like to ask you to create a very simple VI (like a While Loop that displays the iteration terminal), build it to an application, and test the remote depbugging functionality with it.
Kind regards:
Andrew Valko
NI Hungary
03-25-2013 09:40 AM
1. These computers are on the same subnet.
2. Development Computer has Windows Vista
3. I probed int32 data wire also in a simple while loop.
4. I have tested debugging with a simple while loop.
I attached error log.
Computer parameters:
1. Winows Xp.
2. AMD Athlon XP 2000+ 1,67Ghz
3. 1,50 Gb RAM
4. 4Gb free space on system drive.
07-25-2014 04:26 AM
Hi all!
Any solutions to this issue?
I'm having the same problem debugging an app on WIN XPe target.
11-03-2014 01:16 PM
I have the same problem, windows xp (target machine), with windows 7 (localhost machine). LabVIEW 2014 Developer Suite Edition. Wire attempting to probe is an error cluster.
On my instance, I have to force kill LV on both machines to recover. I do not get any errors displayed or etc, the process just stops dead