Osvaldo Ogliari Posted March 20, 2012 Report Share Posted March 20, 2012 (cross-posted on LavaG.org) Hello to all, boys, I'm using VIPM ver 2011.0.1 (build 1692) dic 07/2011 Community Edition with OpenG Builder ver 3.0.1-2. I am trying to create a package to a library for LabVIEW 2011 that uses recursion native, but Package Builder gives me the same problem described by Kring to "Known Issue (Case 8006): VI Package build hangs in LabVIEW 2009 when recursive VIs included in package" and stated fixed from version 3.0 and later ... I think in my case the problem is that recursion is not "direct" ... Let me explain ... In my library there is the following sequence of calls: VI_A call VI_B that call VI_C that call VI_A! If I realize the simple recursion VI_A call VI_A, the Package Builder executes with success, but building my library, it fail waiting infinitely for the VI to load in memory... the same issue reported by Normandine... Even in may case, I have to kill the process. I do not know if Package Builder maintains a global list of calls, but I think the problem may reside in the test that checks for the sub-VI called the list of callers ... I'm sorry it could not provide a possible solution ... :-( Thank to all! Osvaldo Link to comment Share on other sites More sharing options...
Ashish Posted March 26, 2012 Report Share Posted March 26, 2012 Osvaldo, Thanks for documenting your observations. I was able to recreate the issue and have filed it under Case 13224 for consideration by our VIPM Group. We will keep you posted about the resolution on this issue. Link to comment Share on other sites More sharing options...
Osvaldo Ogliari Posted March 27, 2012 Author Report Share Posted March 27, 2012 Osvaldo, Thanks for documenting your observations. I was able to recreate the issue and have filed it under Case 13224 for consideration by our VIPM Group. We will keep you posted about the resolution on this issue. Thanks! I will stay tuned for the patch! Osvaldo Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted September 25, 2012 Report Share Posted September 25, 2012 We've been working on this issue and will have a fix in the next VIPM Service Pack release. If you need a fix sooner for this issue. Please send a ticket here. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.