PI24097: MEMORY MAPPING FILES IN DYNAMIC VIEWS MAY INCORRECTLY INTERPRET FILE SIZES

Rational ClearCase Fix Pack 6 (8.0.1.6) for 8.0.1
Rational ClearCase Fix Pack 13 (8.0.0.13) for 8.0
Rational ClearCase Fix Pack 14 (8.0.0.14) for 8.0
Rational ClearCase Fix Pack 7 (8.0.1.7) for 8.0.1
Rational ClearCase Fix Pack 15 (8.0.0.15) for 8.0
Rational ClearCase Fix Pack 8 (8.0.1.8) for 8.0.1
Rational ClearCase Fix Pack 16 (8.0.0.16) for 8.0
Rational ClearCase Fix Pack 9 (8.0.1.9) for 8.0.1
Rational ClearCase Fix Pack 17 (8.0.0.17) for 8.0
Rational ClearCase Fix Pack 10 (8.0.1.10) for 8.0.1
Rational ClearCase Fix Pack 18 (8.0.0.18) for 8.0
Rational ClearCase Fix Pack 11 (8.0.1.11) for 8.0.1
Rational ClearCase Fix Pack 19 (8.0.0.19) for 8.0
Rational ClearCase Fix Pack 12 (8.0.1.12) for 8.0.1
Rational ClearCase Fix Pack 20 (8.0.0.20) for 8.0
Rational ClearCase Fix Pack 13 (8.0.1.13) for 8.0.1
Rational ClearCase Fix Pack 21 (8.0.0.21) for 8.0
Rational ClearCase Fix Pack 14 (8.0.1.14) for 8.0.1
Rational ClearCase Fix Pack 15 (8.0.1.15) for 8.0.1
Rational ClearCase Fix Pack 16 (8.0.1.16) for 8.0.1
Rational ClearCase Fix Pack 17 (8.0.1.17) for 8.0.1
Rational ClearCase Fix Pack 18 (8.0.1.18) for 8.0.1
Rational ClearCase Fix Pack 19 (8.0.1.19) for 8.0.1
Rational ClearCase Fix Pack 20 (8.0.1.20) for 8.0.1
Rational ClearCase Fix Pack 21 (8.0.1.21) for 8.0.1
Rational ClearCase Fix Pack 22 (8.0.1.22) for 8.0.1
Rational ClearCase Fix Pack 23 (8.0.1.23) for 8.0.1
Rational ClearCase Fix Pack 24 (8.0.1.24) for 8.0.1
Rational ClearCase Fix Pack 25 (8.0.1.25) for 8.0.1

APAR status

• Closed as program error.

Error description

• When performing a build using compilers that map their source
  files to shared memory regions ("memory mapping") in an IBM
  Rational ClearCase dynamic view on a Microsoft Windows host, the
  compile may appear to read past the end of the file, causing
  errors similar to:
  ../../../../dir1/dir2/dir3/Myfile.cpp:27764: stray '\347' in
  program
  ../../../../dir1/dir2/dir3/Myfile.cpp:27764: stray '\1' in
  program
  ../../../../dir1/dir2/dir3/Myfile.cpp:27856:84: null
  character(s) ignored
  ../../../../dir1/dir2/dir3/Myfile.cpp:27764: stray '\4' in
  program
  ../../../../dir1/dir2/dir3/Myfile.cpp:27764: stray '\36' in
  program
  ../../../../dir1/dir2/dir3/Myfile.cpp:27764: stray '\2' in
  program
  ../../../../dir1/dir2/dir3/Myfile.cpp:27764: stray '\350' in
  program
  ../../../../dir1/dir2/dir3/Myfile.cpp:27764: stray '\1' in
  program
  ../../../../dir1/dir2/dir3/Myfile.cpp:27856:92: null
  character(s) ignored
  ../../../../dir1/dir2/dir3/Myfile.cpp:27764: stray '\4' in
  program
  
  In the above example, the file is only 27,724 lines long, so in
  this case the compiler is reading at least 2 lines past EOF.
  Additionally the "\4" indicates that the compiler is attempting
  to interpret random binary data as source code.
  
  Analysis to date shows that this occurs only in versions using
  the recently introduced Windows MVFS redesign: 7.1.2.13,
  8.0.0.9, 8.0.1.2 and later.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users building software in dynamic views on Microsoft        *
  * Windows.                                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When performing a build using compilers that map their       *
  * source files to shared memory regions ("memory mapping") in  *
  * an IBM                                                       *
  * Rational ClearCase dynamic view on a Microsoft Windows host, *
  * the compile may appear to read past the end of the file,     *
  * causing                                                      *
  * errors related to unexpected characters read in the source.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• A problem with correct determination of the size of some mapped
  memory regions is fixed in ClearCase 8.0.0.13 and 8.0.1.6.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  CLEARCASE WIN

• Fixed component ID

  5724G2900

Applicable component levels

• R800 PSY

     UP

• R801 PSY

     UP