Patch-ID# 101752-08 Keywords: XGL, unstripped, libraries, bug, fixes Synopsis: XGL 3.1: XGL Jumbo Patch Date: May/04/95 Solaris Release: 2.4 SunOS Release: 5.4 Unbundled Product: graphics Unbundled Release: BugId's fixed with this patch: 1132564 1132564 1170261 1169096 1168951 1169626 1169287 1168731 1170276 1171640 1168582 1171702 1172444 1175513 1174060 1176335 1178003 1176333 1171404 1176285 1180073 1176116 1179602 1176656 1181275 1176116 1165947 1178548 1181797 1182918 1181822 1176335 1165947 1180073 1184808 1180099 1177897 1187656 1184915 1190799 1192358 1192900 1194656 1195998 Changes incorporated in this version: 1194937 1198408 1193063 1193544 1193666 1174903 Relevant Architectures: sparc Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: 102057-12 or higher Obsoleted by: x495 Files included with this patch: SUNWits/Graphics-sw/xgl/lib/libxgl.so.3 SUNWits/Graphics-sw/xgl/lib/pipelines/xglSUNWcfb.so.4 SUNWits/Graphics-sw/xgl/lib/pipelines/xglSUNWcg6.so.4 SUNWits/Graphics-sw/xgl/lib/pipelines/xglSUNWcgm.so.4 SUNWits/Graphics-sw/xgl/lib/pipelines/xglSUNWmem.so.4 SUNWits/Graphics-sw/xgl/lib/pipelines/xglSUNWswp.so.4 SUNWits/Graphics-sw/xgl/lib/pipelines/xglSUNWxpex.so.4 Problem Description: This patch corresponds to the unstripped version of the patch libraries. That is, this patch provides a set of unstripped .so's, which can be used to obtain a stack trace from a core file created by an XGL application. The stripped version of the patch is Patch 101753-08. The stripped .so's are what are installed from the Solaris 2.4 CD. The following bugs are fixed in this patch: (Rev 01) 1132564 - XGL .so's shipped with RTE is stripped to accommodate upgrade 1170261 - Swp changes to context attrs are sometimes not communicated to dps 1169096 - GX clears entire screen z-buffer, but has to clear a dc viewport 1168951 - XGL application fails on GT and ZX with error "plm: unknown point type" 1169626 - XGL application crashes in use_pt_lists when modelclipping stroke text 1169287 - Polygon decomposition problems 1168731 - When copy from mem_ras to win_ras xgl_context_copy_raster() don't work correctly 1170276 - swp li2MultiPolyline causes dp core dump when rendering wide lines 1171640 - X/PEX server crashed in xgl_triangle_strip on GX/GX+ (Rev 02) 1168582 - NURBS with tim curves can core dump XPDGS-BSPLINE-PROB 1171702 - X/PEX server on GX+ improperly retain the state set by previous PEX client 1172444 - hidden edges show up on multiple frame buffers in xgl_polygon() 1175513 - polylines can sometimes not be rendered when deferral mode is ASTI 1174060 - XGL may not work with ProWorks 3.0.1/ProCompiler C++ 4.0.1 1176335 - Memory leaks in texture mapping 1178003 - Copy Buffer does not work w/zbuffer 1176333 - Purify shows many bad memory accesses 1171404 - X error generated in setting CMAP_NAME of an 8 bits pseudoColor cmap on ZX 1176285 - invalid XGLHOME causes server to die when initializing the PEX extension 1180073 - xgl_multi_simple_polygon point type is wrong after gx punt to swp 1176116 - invalid operation FPE in some xgl_multipolyline and polygons 1179602 - stroke text color bug. certain characters stuck in green (Rev 03) 1176656 - quadmesh with facet colors draws incorrectly on GX 1181275 - clipping is wrong when windows overlap only on the frame 1176116 - Invalid operation FPE in some xgl_multipolyline and polygons 1165947 - NURBS leak memory 1178548 - rgb memory to cg6 copy_buffer() slow 1181797 - cmap uses cmapDrawable after it has been destroyed 1182918 - cg3 fails to draw lines if length is only one pixel 1181822 - internal impl of xgl texturing does not support fast HW texturing 1176335 - Memory leaks in texture mapping (Rev 04) 1165947 - invalid memory access 1180073 - xgl_multi_simple_polygon point type is wrong after gx punt to swp 1184808 - floating point exceptions from xgl_context_new_frame 1180099 - SEGV when drawing large circles (Rev 05) 1177897 - add XGL_EDGE_Z_OFFSET env var to GX pipeline 1187656 - FPE occurs after a call to xgl_polygon when running ProE (Rev 06) 1184915 - wrong rendering when U or V order > 9 1190799 - xgl_context_copy_buffer() segv with memory raster width < 4 to GX (Rev 07) 1192900 - modified check for flushing plist for wireframe 1192358 - malloc unlock problem when running PEX graphics 1194656 - app core dump when GX punt to sw fall back 1195998 - Rendering via swp, clist_rect is ignored when doing single buffering (Rev 08) 1194937 - NPGL demo does not work when run across the net on a pex server 1198408 - XGL 3.1 library unable to load some XGL 3.2 loadable pipelines 1193063 - Graphics in multiple viewports is incorrect when doing double buffering on GX+ 1193544 - Multiple Viewports get the wrong clip rectangle on the GX+ and TGX+ 1193666 - copy_buffer double buffering does not work with OW patch34 for Solaris2.3 on GX+ 1174903 - copy_buffer from draw_buffer to display_buffer broken for GX+ Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions appended to this section. Other specific or unique installation instructions may also be necessary and should be described below. Special Install Instructions: ----------------------------- The two packages supplied in this patch require about 2.2 Mbytes of additional disk space in the partition where XGL is installed. The temporary location, /var/sadm/patch, must have 4.5 MBytes available in order for installpatch to work successfully. An error message will be printed if not enough space is available in /var/sadm/patch. Instructions to install patch using "installpatch" -------------------------------------------------- 1. Become super-user. 2. Apply the patch by typing:
.
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
patch packages failed. Any previously installed packages
in the patch should have been removed. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Patch Installation Messages:
---------------------------
Note: the messages listed below are not necessarily considered errors
as indicated in the explanations given. These messages are, however,
recorded in the patch installation log for diagnostic reference.
Message:
Package not patched:
PKG=SUNxxxx
Original package not installed
Explanation: One of the components of the patch would have patched a
package that is not installed on your system. This is not
necessarily an error. A Patch may fix a related bug for several
packages. Example: suppose a patch fixes a bug in both the
online-backup and fddi packages. If you had online-backup installed
but didn't have fddi installed, you would get the message
Package not patched:
PKG=SUNWbf
Original package not installed
This message only indicates an error if you thought the package
was installed on your system. If this is the case, take the
necessary action to install the package, backout the patch (if
it installed other packages) and re-install the patch.
Message:
Package not patched:
PKG=SUNxxx
ARCH=xxxxxxx
VERSION=xxxxxxx
Architecture mismatch
Explanation: One of the components of the patch would have patched a
package for an architecture different from your system. This is not
necessarily an error. Any patch to one of the architecture specific
packages may contain one element for each of the possible
architectures. For example, Assume you are running on a sun4m. If
you were to install a patch to package SUNWcar, you would see the
following (or similar) messages:
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4c
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4d
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4e
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
The only time these messages indicate an error condition
is if installpatch does not correctly recognize your architecture.
Message:
Package not patched:
PKG=SUNxxxx
ARCH=xxxx
VERSION=xxxxxxx
Version mismatch
Explanation: The version of software to which the patch is applied is
not installed on your system. For example, if you were running Solaris
5.3, and you tried to install a patch against Solaris 5.2, you would
see the following (or similar) message:
Package not patched:
PKG=SUNWcsu
ARCH=sparc
VERSION=10.0.2
Version mismatch
This message does not necessarily indicate an error. If
the version mismatch was for a package you needed patched, either
get the correct patch version or install the correct package version.
Then backout the patch (if necessary) and re-apply.
Patch Backout Errors:
---------------------
Error message:
Patch has not been successfully applied to this system.
Explanation and recommended action: The user has attempted to back
out a patch that was never applied to this system. It is
possible that the patch was applied, but that the patch
directory /var/sadm/patch/ was deleted somehow.
If this is the case, the patch cannot be backed out. The
user may have to restore the original files from the
initial installation CD.
Error message:
This patch was obsoleted by patch $1.
Patches must be backed out in the order in
which they were installed. Patch backout aborted.
Explanation and recommended action: The obsoleted contents of an
older patch rev that apparently still exists under /var/sadm/patch
should never be restored out of sequence. This could undermine
the integrity of the more current patch rev installed and the
restoration of the files it has saved.
Error message:
Patch was installed without backing up the original
files. It cannot be backed out.
Explanation and recommended action: Either the -d option of
installpatch was set when the patch was applied, or the save
area of the patch was deleted to regain space. As a result, the
original files are not saved and backoutpatch cannot be used. The
original files can only be recovered from the original
installation CD.
Error message:
pkgrm of package failed return code .
See /var/sadm/patch//log for reason for failure.
Explanation and recommended action: The removal of one of
patch packages failed. See the log file for the reason for
failure. Correct the problem and run the backout script again.
Error message:
Restore of old files failed.
Explanation and recommended action: The backout script uses the
cpio command to restore the previous versions of the files
that were patched. The output of the cpio command should
have preceded this message. The user should take the
appropriate action to correct the cpio failure.
KNOWN PROBLEMS:
On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT. See instructions above for
applying patches to a client.
A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk)
could affect the reliability of installpatch or backoutpatch
which uses package utilities to install and backout the patch
package. It is recommended that any patch that fixes package
utility problems be reviewed and, if necessary, applied before
other patches are applied. Such existing patches are:
100901 Solaris 2.1
101122 Solaris 2.2
101331 Solaris 2.3
SEE ALSO
pkgadd, pkgchk, pkgrm, pkginfo, showrev