LabVIEW Base Development System 8.5.1 - Windows/2000/Vista x64/Vista x86/XP - 8.5.1f4 Patch

3 ratings | 3.67 out of 5

Print Document

LabVIEW 8.5.1 patch for a web server security issue and several other distinct issues as described below.

Description

The LabVIEW 8.5.1f4 patch for Windows includes fixes from LabVIEW 8.5.1f1, 8.5.1f2, and 8.5.1f3, as well as two additional fixes.

New Issues Fixed in 8.5.1f4

• Fixed a security issue with the LabVIEW Web Server where the use of relative paths allows read-only access to files outside of the Web Server directory. In LabVIEW 8.5 and versions of 8.5.1 prior to this patch, machines allowed to access the LabVIEW Web Server can access files outside of the server root directory if they send the appropriate GET command and use the proper relative path. Use the Web Server: Configuration page of the Options dialog box to configure the Web Server. Use the Web Server: Browser Access page of the Options dialog box and non-NI security such as firewalls to configure access to the Web Server. This issue does not affect LabVIEW 8.2.1 or earlier or LabVIEW 8.6 and later. This issue was tracked through NI bug ID 125230.
• Fixed an issue where, on slower computers, placing a breakpoint on a VI downloaded to RT or creating a probe on VIs downloaded to RT might cause the LabVIEW host process to crash. Some user actions can translate to synchronous calls from the LabVIEW host process to the program running on the real-time target. Several of these synchronous calls can execute at the same time, but with slower targets or a lack of CPU or network bandwidth, the calls might not complete quickly enough, resulting in a fatal internal error and a LabVIEW crash. The crash occurs only in the host LabVIEW development environment and not in applications built with the run-time engine. If you use NI TestStand to deploy VIs to an RT target, replace lvffrt.dll, listed in the Patched LabVIEW Files section, to apply the patch. This issue was tracked through NI bug ID 124176.
  

Fixed an issue where a crash occurs during the following scenario where Example1.dll, saved in LabVIEW 8.6, calls a function in the LabVIEW Run-Time Engine and Example2.dll, saved in LabVIEW 8.5, calls Example1.dll:

1. A VI directly loads Example1.dll, which calls a function in the LabVIEW 8.6 Run-Time Engine.
2. Another VI loads Example2.dll, which indirectly loads Example1.dll for a second time.

On the second load, Example1.dll cannot determine whether to call a function in the LabVIEW 8.6 Run-Time Engine or the LabVIEW 8.5 Run-Time Engine. The LabVIEW 8.6 Run-Time Engine is associated with the initial load of Example1.dll. The LabVIEW 8.5 Run-Time Engine is associated with Example2.dll, which loads Example1.dll in step 2. This situation is uncommon, however, it is possible to encounter this issue with any combination of LabVIEW versions 8.0 or later. This issue was tracked through NI bug ID 114195.

• Fixed an issue where LabVIEW does not generate a Mouse Down event when you right-click a disabled control if a subpanel control hosts the VI. If a VI includes an Event structure configured to record Mouse Down events, the event should generate any time you press a mouse button and return a number that corresponds to the button you click. This issue was tracked through NI bug ID 54966.
• Fixed an issue where LabVIEW does not generate Mouse Down events when you right-click a disabled control if the control is part of a control grouping. This issue is similar to the previous one. However, in this case, the issue does not depend on a subpanel container hosting the VI. LabVIEW does not generate Mouse Down events on any disabled control that is part of a control group. Use the Reorder pull-down menu on the front panel toolbar to configure control groups. This issue was tracked through NI bug ID 98256.
• Fixed a performance problem that results in a substantial LabVIEW slowdown when a subpanel control contains a VI and LabVIEW rapidly updates the controls in the VI. When you update a control with a value and the UI is visible, LabVIEW redraws the control and checks whether the control overlays other controls that LabVIEW also must redraw. The section of code that determines whether controls are overlaid incorrectly determines which controls need to be redrawn if a subpanel control contains the VI. This issue causes LabVIEW to redraw all controls on subpanel VIs every time any control value changes and results in performance degradation. This issue was tracked through NI bug ID 54966.

Fixed an issue where assigning timed loops to multiple CPUs results in a LabVIEW crash. Assigning several timed loops to multiple CPUs halts code execution and causes LabVIEW to exit suddenly. This crash occurs only on Windows systems with more than four cores. This issue was tracked through NI bug ID 55660.

For additional information on any of the issues described, contact National Instruments support through direct email or phone and have the NI bug ID available.

Installation Instructions

This patch does not have an installer. See readme_LV851f4.html for installation instructions and system requirements.

Install Notes

If you install this patch, you do not need to install the 8.5.1 Multicore Timed Loop patch also available through drivers and updates.

Your Feedback

Rate this document: Select a rating! 1 2 3 4 5
Answered Your Question? Yes No