Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 0434 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 0434.

Report 0434 Actions

    Problem Report Number 0434
    Submitter's Classification Specification problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0053
    Raised 1994-04-05 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Internationalised System Calls and Libraries (XPG4)
    Certification Program The Open Brand certification program
    Test Suite VSX4 version 4.3.2
    Test Identification XPG4.os/ipc/T.shmat 2
    Problem Summary PG4R.053 According to X/Open CAE Specification, System Interfaces and Headers, Issue 4 page 369. The shmat() function will fail if: [EINVAL] The shmaddr is not a null pointer and the value of (shmaddr - (( ptr...
    Problem Text
    According to X/Open CAE Specification, System Interfaces and Headers, Issue 4
    page 369.

    The shmat() function will fail if:
    [EINVAL] The shmaddr is not a null pointer and the value of (shmaddr - ((
    ptrdiff_t)shmaddr%SHMLBA)) is an illegal address for attaching shared memory.

    Our implementation will meet the above condition in this test case. In another
    word that the value of (shmaddr - ((ptrdiff_t)shmaddr%SHMLBA)) is an illegal
    address for attaching shared memory, therefore, EINVAL was returned.
    Test Output
    /tset/XPG4.os/ipc/shmat/T.shmat 2 Failed

    Test Information:
    shmat(shmid2, 0x800fe800, SHM_RND) failed, returned 0xffffffff with
    errno 22 (EINVAL)

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    I am not clear why this is claimed to be an ambiguity in the X/Open
    Specification; the issue seems to relate to whether the test suite is
    using a valid address for attaching shared memory or not. This may be
    a test suite fault, but without further information I am not able to
    properly assess this. It may be that the test suite assumes that shared
    memory segments are attached at low memory addresses when no address is
    given and that the calculation of the address for the attach which fails
    produces an invalid address.

    I suspect that the request is a valid one, but without more information
    I am unable to come to an informed decision. I suggest that this request
    is resubmitted with more detailed analysis of the problem. At the moment,
    I do not feel able to recommend that the request be granted.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority