Jump to content

Broken code with no broken arrow.


Recommended Posts

Not sure what causes this but I've experienced this several times lately.

I run a toplevel VI several times and somewhere I get an error on the error cluster. So I decide to start debugging by opening up the subVI's. When I open one of the subVI's I notice that it has a broken run arrow and now I also notice that my toplevel VI has a broken run arrow. How is it possible for LabVIEW to run broken code? The only thing I can think of is that the broken code has not propogated to the current running application instance until I open it up. Not sure why however since I only have one instance. I have the project environment open too.

Link to comment
  • 8 months later...

QUOTE (Aristos Queue @ Aug 20 2008, 02:42 AM)

You have filed a CAR, right?

Have you ever tried to file a CAr without being able to reproduce the issue on demand?

I have seen a couple of those myself, also working LV 8.5. I'm not using globals so if its the same bug I have seen it is not due them. THe other observation that I can add is that a really fuzzy general type observation. I would swear (if pressed) that code changes are not propagating to all of the VI's that are not open. I say this because I work with a tree.VI open and after amking changes (but before running) I save everything (from tree.vi save all) then close the tree.vi. Backup then re-open and test the code. WHen closing the tree.vi, I see VI's that want to be saved. As a result I ahve resorted to an old habit of opening and closing the tree a couple of times to make sure all of the changes get propogated.

Just reporting what I have ben seing.

Ben

Link to comment

QUOTE (neB @ Aug 20 2008, 05:36 AM)

I agree. Reporting this to NI is a futile exercise. Not reproducible at all.

QUOTE (neB @ Aug 20 2008, 05:36 AM)

I would swear (if pressed) that code changes are not propagating to all of the VI's that are not open. I say this because I work with a tree.VI open and after amking changes (but before running) I save everything (from tree.vi save all) then close the tree.vi. Backup then re-open and test the code. WHen closing the tree.vi, I see VI's that want to be saved. As a result I ahve resorted to an old habit of opening and closing the tree a couple of times to make sure all of the changes get propogated.

Ben, there's a thread for this issue here.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.