IBM Support

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

Subscribe

You can track all active APARs for this component.

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 number

    PI24097

  • Reported component name

    CLEARCASE WIN

  • Reported component ID

    5724G2900

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-08-18

  • Closed date

    2014-12-10

  • Last modified date

    2014-12-10

  • 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



Document information

More support for: Rational ClearCase

Software version: 801

Reference #: PI24097

Modified date: 10 December 2014