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

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 0444 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 0444.

Report 0444 Actions

    Problem Report Number 0444
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0063
    Raised 1994-05-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/msgsnd 2
    Linked Problem Reports TSD4.064, TSD4.130, (in, old, system)
    Problem Summary PG4R.063 There is a problem in msgsnd.c in that the parent process sends the child a a SIGUSR1, tidies up and returns. The child process catches the SIGUSR1 signal and exits. However, when the parent process r...
    Problem Text
    There is a problem in msgsnd.c in that the parent process sends the
    child a a SIGUSR1, tidies up and returns. The child process catches the
    SIGUSR1 signal and exits. However, when the parent process returns to
    tet_fork (called from cpsig) it sends a SIGTERM to the child process.
    In a multi-processor system this may happen before the child has had
    time to exit. This causes the test to be "UNRESOLVED."
    The problem would be fixed by the parent process giving the child some
    time to exit before returning to tet_fork. A delay as short as 40
    milliseconds is enough.
    Test Output
    ************************************************************************
    /tset/XPG4.os/ipc/msgsnd/T.msgsnd 2 Unresolved

    Test Description:
    When there is insufficient space in the queue or the system to send
    the message pointed to by msgp and the IPC_NO_WAIT flag is clear in
    msgflg, then a call to msgsnd(msqid,msgp,msgsz,msgflg) suspends the
    calling process.

    Test Information:
    unexpected signal 15 (SIGTERM) received
    ************************************************************************

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    This is the same problem as reported under TSD4.130 which should be
    quoted when submitting a branding application.

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

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority