LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Prevent vi running when opened

Solved!
Go to solution

Hi,

I have a vi in which I've made a mistake with the pointer allocation in to a Call Library Node block. When I tried to run the vi, LabView crashed. 

Now when I try to open the vi again, it immediately crashes with 'Exception: Access violation (0xC0000005) at EIP=0x01CA3B32. It isn't reaching the vi GUI window or the edit window.

 

Is there a way to prevent the vi from allocating memory when opening. I'm surprised it is even doing this considering the code isn't even running! 

 

Thanks in advance. 

0 Kudos
Message 1 of 3
(3,047 Views)
Solution
Accepted by topic author Miakatt

Not sure if this is what you need, but you can open a new VI and drop your problem VI onto its block diagram. Then you should be able to right click it and edit properties.

Message 2 of 3
(3,015 Views)

Hi Gregory,

 

Thanks for the suggestion. Unfortunately, the error I've introduced is in the master vi, which contains around 15 sub-vi's. I can drag any of the sub vi's to a blank vi and open as you suggest. But when I try to do this with my master vi, my laptop cannot handle it and LabView stops responding. 😞

 

I've installed an evaluation copy of LabView on my Macbook and can open the master vi. So at least I have a vi to copy from (by hand). So it looks like that's the quickest solution.  Now back to the original problem of trying to understand how to pass a pointer to a call library node and obtain the data from the buffer that the pointer points to..! 

 

Thanks for your help. 

0 Kudos
Message 3 of 3
(2,975 Views)