========================================================================== The checksum's (found through sum -r) of the files that you have received (other than this README) are as follows: 14990 2 patchSG0002995 25336 1212 patchSG0002995.compiler_eoe_sw 47924 2 patchSG0002995.idb ========================================================================== - 1 - 1. Patch_SG0002995_Release_Note This release note describes patch SG0002995 to IRIX 5.3. 1.1 Supported_Hardware_Platforms This patch contains bug fixes for all platforms. The software cannot be installed on other configurations. 1.2 Supported_Software_Platforms This patch contains bug fixes for IRIX 5.3 for all platforms. The software cannot be installed on other configurations. This patch replaces patches SG0000231, SG0000342, SG0001335, SG0001479, SG0002064, and SG0002403. 1.3 Bugs_Fixed_by_Patch_SG0002995 This patch contains fixes for the following bugs. Bug numbers from the Silicon Graphics bug tracking system are included for reference. o Bug #573829 rld was failing to treat delay-loaded libraries correctly on a dlclose() which could prematurely unmap a DSO that was delay-loaded from the dlopened object, but was actually loaded by some other dlopen (not delay-loaded there). Specifically, /usr/sbin/dirview could coredump when one clicked on the small face icon (Gallery Mode). o Bug #554173 rld was corrupting its private malloc arena at times. The fix for 521237 mentioned below was not completely correct, and this fixes that fix. Patch SG0002403 (the patch before this patch) contained the following bug fixes (these are retained). o Bug #521237 If in its normal search for DSOs rld could not find a DSO in the first couple of directories it looked into it could core dump. And it had other problems in its own malloc arena (an arena separate from the malloc arena of app rld is running) which could lead to coredumps. These problems existed in in patches 1479 and 2064 but not (as far as is known) in earlier other IRIX releases or patches. o Bug #493007 In patches 1479 and 2064 (and only with those patches), a leading : in the LD_LIBRARY_PATH could make rld coredump. - 2 - Patch SG0002064 (the patch before 2403) contained the following bug fixes (these are retained). o Bug #482870 -- When running a setuid/setgid program rld could be tricked into creating a security hole. Now rld ignores the -log option of the _RLD_ARGS environment variable for setuid/setgid programs unless the real user is root (in addition, rld continues to ignore some environment variables when handling setuid/setgid programs run by non-root users to avoid security holes). o Bug #250597 -- rld missing last symbol when relocating dlopen'ed DSO's. What actually happened was that rld was resolving symbols for dlopen'ed DSO's incorrectly when a previous dlsym returned a zero value. This bug was seen when running Wavefront. o Bug #258422 -- rld would block in a multi-threaded, context when one thread attempted a dlopen of a shared object which then had initialization code that required use of a lazy text resolution. This manifested it self as a hang when certain plugins were requested in a particular order. o Bug #361758 -- rld loops when 2 delay-loaded libraries are linked into the same executable and the 2 libraries are inter-dependent on each other. Also, the performance of the libdl routines are not acceptable in big applications when hundreds of libraries are loaded using dlopen calls. o Bug #337982 -- Specifying LD_LIBRARY_PATH with more than approximately 500 characters causes rld to dump core. o Bug #364118 -- rld loops in dlsym call. o Bug #290198 -- rld loops when dlopen'ing libraries that have inter-dependencies. o Bug #393148 -- netscape gets unresolvable symbol in /usr/lib/libSgm.so.1: fiRenderX when attempting save- file on vrml scene. o Bug #402975 -- memory leak in rld when performing dlopen/dlclose. - 3 - 1.4 Subsystems_Included_in_Patch_SG0002995 This patch release includes these subsystems: o patchSG0002995.compiler_eoe_sw.unix 1.5 Installation_Instructions Because you want to install patches for only the problems you have encountered, patch software is not installed by default. After reading the descriptions of the bugs fixed in this patch, determine the patches that meet your specific needs. Patch software is installed like any other Silicon Graphics software product. Follow the instructions in your IRIS Software Installation Guide to bring up the miniroot form of the software installation tools. Follow these steps to select a patch for installation: 1. At the Inst>prompt, type install patchSGxxxxxxx where xxxxxxx is the patch number. 2. Select the desired patches for installation. 3. Initiate the installation sequence. Type Inst> go 4. You may find that two patches have been marked as incompatible. If this occurs, you must deselect one of the patches. Inst> keep patchSGxxxxxxx where xxxxxxx is the patch number. 5. After completing the installation process, exit the inst program by typing Inst> quit To remove a patch, use the versions remove command as you would for any other software subsystem. The removal process reinstates the original version of software unless you have - 4 - specifically removed the patch history from your system. versions remove patchSGxxxxxxx where xxxxxxx is the patch number. To keep a patch but increase your disk space, use the versions removehist command to remove the patch history. versions removehist patchSGxxxxxxx where xxxxxxx is the patch number.