ECO NUMBER: CXXSHRDAE01306 ----------- PRODUCT: DEC OSF/1 Operating System -------- UPDATED PRODUCT: DEC OSF/1 Operating System 3.0 ---------------- APPRX BLCK SIZE: 846 ---------------- COVER LETTER 1 KIT NAME: CXXSHRDAE01306 2 KIT DESCRIPTION: 2.1 Version(s) of DEC OSF/1 to which this kit may be applied: V3.0, V3.2 2.2 Kits superseded by this kit: None 2.3 Files patched or replaced: o /usr/lib/cmplrs/cxx/libcxx.so (new image) o /usr/lib/cmplrs/cxx/libcomplex.so (new image) o /usr/lib/cmplrs/cxx/libtask.so (new image) o /usr/shlib/libcxx.so (new symbolic link) o /usr/shlib/libcomplex.so (new symbolic link) o /usr/shlib/libtask.so (new symbolic link) 3 PROBLEMS ADDRESSED IN CXXSHRDAE01306 KIT o The >> operator within the istrstream class now works correctly when converting from a character string to a float. o An access violation or segmentation fault is no longer generated when your application writes into an uninitialized ostream_withassign. Instead the written text is simply ignored. o -- COVER LETTER -- Page 2 27 April 1995 A file positioning problem for bidirectional fstreams has been corrected. Previously if your application switched from reading an fstream to writing an fstream, with or without an intervening seek operation, the necessary synchronization of the external file position with the get pointer was often skipped. This resulted in the written data being placed incorrectly within the file. o The real() function within the stopwatch class was incorrectly returning the CPU time. Now it returns the clock time as documented. o The flush() function within the ostream class was incorrectly calling overflow(). Now flush() calls sync() as documented. o During the destruction of a Message object, the value of the LANG environment variable is no longer cleared. o Instances of ostrstream no longer delete their strstreambuf twice. This had no effect on the standard memory allocators, but it did cause problems for some third party memory allocators. o The conflict between the clog variable within the math library and clog within the class libraries has been resolved. The segmentation fault in sync_with_stdio() no longer occurs. o The strstreambuf destructor no longer deletes the buffer if str() has been called. As documented, the str() function now transfers the responsibility of freeing the buffer to the caller. o The >> operator within the istrstream class now works correctly when the conversion base format is hex and hexadecimal values are read which begin with "0" but are not prefixed with "0x". o A segmentation fault no longer occurs during image exit for applications which called sync_with_stdio(). Previously, the call to sync_with_stdio() would free memory which was again freed at image exit; this sometimes generated a segmentation -- COVER LETTER -- Page 3 27 April 1995 fault. o The algorithm used by ostrstream for dynamic allocation has been corrected. The previous algorithm doubled the buffer size each time additional space was needed, and this resulted in very inefficient use of memory for large buffers. 4 INSTALLATION INSTRUCTIONS: This DEC C++ Class Library kit may be installed on DEC OSF/1 V3.0 and V3.2. The tar file, CXXSHRDAE01306.tar, must be unpacked before using the setld utility to install the kit. When you unpack the tar file, you will find the release notes in a separate file, CXXSHRDAE01306.relnotes. After unpacking the tar file, install this kit with the setld utility by logging into the root account and typing the following: /usr/sbin/setld -l [location of the unpacked files] Copyright Digital Equipment Corporation 1995. All Rights reserved. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. This ECO has not been through an exhaustive field test process. Due to the experimental stage of this ECO/workaround, Digital makes no representations regarding its use or performance. The customer shall have the sole responsibility for adequate protection and back-up data used in conjunction with this ECO/workaround.