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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0126 Actions

    Problem Report Number 0126
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0126
    Raised 1993-11-23 08:00
    Updated 2003-03-13 08:00
    Published 1993-12-08 08:00
    Product Standard Internationalised System Calls and Libraries (XPG4)
    Certification Program The Open Brand certification program
    Test Suite VSX4 version 4.2.4
    Test Identification POSIX.os/procprim/sigconcept 41
    Problem Summary TSD4.126 This test case fails with pseudo-ttys because previous test cases call tty_prep() and loop_prep() directly, without connecting the two pseudo-ttys with ptycon() or closing the master sides of the pseu...
    Problem Text

    This test case fails with pseudo-ttys because previous test cases call
    tty_prep() and loop_prep() directly, without connecting the two pseudo-ttys
    with ptycon() or closing the master sides of the pseudo-ttys when the test
    cases are done with them.

    Test case number 21 just calls tty_prep(), but never closes the master
    side of the pseudo-tty. Test case numbers 30, 31, 34, 35, 36, and 37 each
    tty_prep() and loop_prep(), but neither close the master sides nor connect
    the two pseudo-ttys. When test case number 41 starts to run, it tries to
    open a pseudo-tty loopback. It thinks that there already is an existing
    loopback because the master sides of each pseudo-tty are still open. It
    opens the corresponding slaves and assumes that the processes that are created
    from ptycon() are still running, which were never started before. When
    it writes the interrupt characters to the loop file descriptor, it never
    arrives on the tty side. So the SIGINT signal is never generated.

    Test Output
    **************************************************************************
    ************************************************************************
    /tset/POSIX.os/procprim/sigconcept/T.sigconcept 41 Failed

    Test Description:
    When the process is a controlling process, process termination causes
    the controlling terminal associated with the session to be
    disassociated from the session.
    Posix Ref: Component Signal Concepts Assertion 3.3.1.4-X4(C)

    Test Strategy:
    OBTAIN value for VSX_TERMIOS_TTY using tet_getvar()
    CREATE parent|child process pair
    CHILD process:
    CREATE process session using setsid()
    OPEN and initialise terminal file and loopback file
    SET signal action for SIGINT to signal catching function
    WRITE interrupt character to loop_fildes
    VERIFY that calling process received SIGINT
    TERMINATE process with kill(getpid(),SIGKILL)
    PARENT process:
    WAIT for child process to terminate using wait_child - (tsetlib)
    VERIFY that child process terminated correctly
    CREATE parent|child process pair
    CHILD process:
    CREATE process session using setsid()
    OPEN and initialise terminal file and loopback file
    SET signal action for SIGINT to signal catching function
    WRITE interrupt character to loop_fildes
    VERIFY that calling process received SIGINT
    TERMINATE process with kill(getpid(),SIGKILL)
    PARENT process:
    WAIT for child process to terminate using wait_child - (tsetlib)
    VERIFY that child process terminated correctly

    Test Information:
    process did not receive SIGINT when expected
    child process terminated incorrectly
    expected action: process terminated - signal 9
    observed action: process exitted - exit code 16
    process did not receive SIGINT when expected
    child process terminated incorrectly
    expected action: process terminated - signal 9
    observed action: process exitted - exit code 16
    path tracing error: path counter 3, expected 5
    ************************************************************************
    **************************************************************************

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    This is accepted to be a Test Suite Deficiency.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion
    This is an agreed Test Suite Deficiency.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority