Technical article 109837

What is SLS PTF7123A, the UnixWare/OpenServer Development Kit (UDK) Supplement?

OpenServer 5.0.4OpenServer 5.0.5UnixWare 7.0.0UnixWare 7.0.1

Written · Last revised

Problem

These problems are occurring when running the UnixWare/OpenServer Development Kit (UDK) 7.0.0 on SCO operating systems:

1. Optimizer may use one register for 2 arguments when "unsafe" ASM functions are called, causing bad code to be generated. NOTE: This problem does not exist in UnixWare 7.0.1. Tracking numbers: ul98-03604, 500626

2. A "for" loop with a known range at compile time (constant initial and final values) that contains a sparsely populated "switch" statement with the majority of the "case" blocks ending with a "return" may be incorrectly optimized. Symptoms may appear as early termination of the loop, corruption of a local variable, or incorrect indexing into an array. NOTE: This problem does not exist in UnixWare 7.0.1. Tracking numbers: ul98-03902, 500631

3. Incorrect optimization of a "for" loop containing a NULL pointer check may result in the NULL pointer check getting moved outside the loop, but with subsequent dereference of that NULL pointer remaining inside the loop, causing an application to dump core. NOTE: This problem does not exist in UnixWare 7.0.1. Tracking numbers: ul98-04007, 500627

4. Yacc(1) generated source code contains #line preprocessor directives with the file name of the yacc source file. If the first occurrence of such a #line directive is within a function, it is possible that the file name will be corrupted and possibly result in the corruption of the compiler stack, causing the compiler to core dump. Tracking numbers: ul98-27207, 710645

5. Degenerate unsigned comparisons with zero in a "?:" construct can cause the compiler to core dump in some situations. Tracking numbers: ul98-30722, 500891

6. Intermittent C++ compiler core dumps when compiling the SGI STL. Tracking numbers: ul98-29212, 500874

7. Using the "-Zp1" flag to the C++ compiler with bit fields
may create a structure layout with a bit field that straddles
the base type container boundary.  This may result in incorrect
code to access or modify that bit field.  A symptom of this
problem is an assembler error stating that a "literal value
does not fit" in the assembly instruction coding.
Tracking numbers: ul98-23911, 500819

Solution

Support Level Supplement (SLS) PTF7123A corrects these problems. These files are modified on UnixWare 7 systems:

/usr/ccs/lib/acomp
/usr/ccs/lib/c++be
/usr/ccs/lib/c++fe
/usr/ccs/lib/fe.so
/usr/ccs/lib/optim

These files are modified on SCO UnixWare 2.1.x and SCO OpenServer Release 5 systems:

/udk/usr/ccs/lib/acomp
/udk/usr/ccs/lib/c++be
/udk/usr/ccs/lib/c++fe
/udk/usr/ccs/lib/fe.so
/udk/usr/ccs/lib/optim

See the attached cover letter that accompanies this SLS for more information, including installation instructions.

Dear SCO Customer,

Support Level Supplement (SLS) PTF7123A, the UnixWare/OpenServer Development Kit Supplement, corrects known problems with running the UnixWare/OpenServer Development Kit (UDK) 7.0.0 on SCO operating systems.

SLS PTF7123A contains modified versions of these files on UnixWare 7 systems:

/usr/ccs/lib/acomp
/usr/ccs/lib/c++be
/usr/ccs/lib/c++fe
/usr/ccs/lib/fe.so
/usr/ccs/lib/optim

SLS PTF7123A contains modified versions of these files on SCO UnixWare 2.1.x and SCO OpenServer Release 5 systems:

/udk/usr/ccs/lib/acomp
/udk/usr/ccs/lib/c++be
/udk/usr/ccs/lib/c++fe
/udk/usr/ccs/lib/fe.so
/udk/usr/ccs/lib/optim
Problem Specifics:
------------------

1. Optimizer may use one register for 2 arguments when "unsafe" ASM functions are called, causing bad code to be generated. NOTE: This problem does not exist in UnixWare 7.0.1. Tracking numbers: ul98-03604, 500626

2. A "for" loop with a known range at compile time (constant initial
   and final values) that contains a sparsely populated "switch"
   statement with the majority of the "case" blocks ending with a
   "return" may be incorrectly optimized.  Symptoms may appear as
   early termination of the loop, corruption of a local variable, or
   incorrect indexing into an array.
   NOTE: This problem does not exist in UnixWare 7.0.1.
   Tracking numbers: ul98-03902, 500631

3. Incorrect optimization of a "for" loop containing a NULL pointer check may result in the NULL pointer check getting moved outside the loop, but with subsequent dereference of that NULL pointer remaining inside the loop, causing an application to dump core. NOTE: This problem does not exist in UnixWare 7.0.1. Tracking numbers: ul98-04007, 500627

4. Yacc(1) generated source code contains #line preprocessor directives
   with the file name of the yacc source file.  If the first occurrence
   of such a #line directive is within a function, it is possible that
   the file name will be corrupted and possibly result in the corruption
   of the compiler stack, causing the compiler to core dump.
   Tracking numbers: ul98-27207, 710645

5. Degenerate unsigned comparisons with zero in a "?:" construct can cause the compiler to core dump in some situations. Tracking numbers: ul98-30722, 500891

6. Intermittent C++ compiler core dumps when compiling the SGI STL. Tracking numbers: ul98-29212, 500874

7. Using the "-Zp1" flag to the C++ compiler with bit fields may create
   a structure layout with a bit field that straddles the base type
   container boundary.  This may result in incorrect code to access
   or modify that bit field.  A symptom of this problem is an assembler
   error stating that a "literal value does not fit" in the assembly
   instruction coding.
   Tracking numbers: ul98-23911, 500819

The release notes displayed prior to installation can be found in

/var/sadm/pkg/ptf7123/install/ptf7123.txt
Software Notes and Recommendations
----------------------------------

SLS PTF7123A should only be installed on these SCO products running the UnixWare/OpenServer Development Kit 7.0.0:

UnixWare 7.0.0 with the UnixWare 7 Release Supplement (uw7rs) UnixWare 7.0.1 SCO UnixWare Application Server Release 2.1.2, 2.1.3 SCO UnixWare Personal Edition Release 2.1.2, 2.1.3 SCO OpenServer Enterprise System Release 5.0.4, 5.0.5 SCO OpenServer Host System Release 5.0.4, 5.0.5 SCO OpenServer Desktop System Release 5.0.4, 5.0.5

Testing of the modified software contained in this SLS has been
conducted only to the extent necessary to confirm that it resolves
the problems stated above.  Such testing consists of re-creating
the problem conditions (typically in an SCO test laboratory) and
verifying that the problems no longer occur.  No other testing of
this software has been done.
Installation Instructions
-------------------------

1. Download the ptf7123a.Z file to the /tmp directory on your machine.

2. As root, uncompress the file and add the SLS package to your system using these commands:

$ su
Password: <type your root password>
# uncompress /tmp/ptf7123a.Z
# pkgadd -d /tmp/ptf7123a
# rm /tmp/ptf7123a

3. There is no need to reboot the system after installing this SLS.

Removal Instructions
--------------------

1. As root, remove the SLS package using these commands:

$ su
Password: <type your root password>
# pkgrm ptf7123

2. There is no need to reboot the system after removing this SLS.

If you have questions regarding this SLS, or the product on which it is installed, please contact your software supplier.

We appreciate your business.
SCO Support Services

From the Xinuos technical article database, record 109837. Reproduced with permission. The original is at www.sco.com/ta/109837, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.