8.5 bugs

[aartjan]

LV8.5 bugs after a few hours of playtime..
There probably is a special group for this kind of subject, but i couldn't find it right away. So here goes:

-when asking an rtm file which callers it has, it will falsly claim it has no callers.
-when building a source distribution llb with a new lvlib to contain all the source, it will not find the VI's anymore during the build.
-labview canot detect if an lvlib is corrupted by a crash and will not disconnect member of a corrupted lvlib, thus making it rather hard to fix the problem when it happens.

If I should post this in another thread, let me know. Otherwise I will continue posting my findings in this one.

Aart-Jan

[altenbach]

You might want to post these in the monthly bug thread:

http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=4070&jump=true

[Roy_F]

---

@aartjan wrote:
LV8.5 bugs after a few hours of playtime..
...
If I should post this in another thread, let me know. Otherwise I will continue posting my findings in this one.

---

You should really create a separate thread for each problem you find. That allows people to focus on one issue at a time and keeps things from getting confusing (e.g. "reported to R&D, CAR xxx" - which problem?). If the problem is confirmed to be a bug in the product, you should (within a couple of days) see a posting along the lines of "Problem reported to R&D..." with a CAR (Corrective Action Request) number. That is your confirmation that the problem is in our database and will be "addressed" (could be fixed, could be closed as not a bug, etc.).

The monthly bug threads are something our user community started to help people find all the threads which discuss bugs; hence the encouragement to post a brief statement about a bug there with a link to the thread which will actually discuss that bug. You might want to wait to confirm something is a bug before posting there, but it's not a big deal if an entry gets created and the problem ends up being determined "not a bug". The discussion that leads up to this determination is often helpful.

I'll see if we can't get someone to check on the problems you mentioned above to see if they are already reported, so you might hold off on creating separate threads on them for a day or so.

Thanks for taking the time to help improve LabVIEW and the community by posting this information.

Roy Faltesek
Sr. Group Manager
LabVIEW R&D

[Travis_M.]

Hello Aart-Jan,

Were you able to resolve these 3 issues?  We're still interested in helping out if you haven't already reported those.  If you have reported them, could you post links up to this thread for where you reported them, or maybe just give an update if you were contacted by NI directly.

By posting the results of your investigation, other users reading this post who have the same problem will hopefully be able to find a resolution to their problems more quickly.  Thanks a bunch!