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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1158 Actions

    Problem Report Number 1158
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0360
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Internationalised System Calls and Libraries Extended (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSU version 4.1.1
    Test Identification Base/readv 22
    Problem Summary PG4U.00110 This request argues pty configuration should be modifable by the user.
    Problem Text
    This test, which previously passed in VSU4.1.0, was updated in VSU 4.1.1
    to open a master/slave pty locally, which according to the change comments
    was done to avoid the requirement for physical terminals. This change now
    results in a failure on our implementation.

    Whereas previously the test used user configurable functions in
    CAPI/SRC/LIB/capi_user (which we updated to push specific modules needed
    for tty semantics) all functions are now local to the tests. This prevents
    the user from making implementation specific changes that may be required
    in order to enable tty semantics.

    It is not clear if the test is attempting to test the master side and/or
    the slave side of the pty. In either case, in order to get the tty
    semantics on our implementation, it is necessary to push the ptem, ldterm,
    and ttcompat modules on the stream for the slave side. This would need to
    done in the spty_init() function before the call to tcgetattr(). If the
    test is attempting to test the master side, these modules also need to be
    pushed on the master side as well. This would be in the mpty_prep() function
    just before the calls to fcntl(). If the test is only testing the slave side,
    then rather than pushing the modules on the master side, the call
    to tcsetattr() in the main function needs to be upated to use the slave
    side, not the master side.

    Regardless of whether or not either one or both of these (slave vs master) is
    being tested, the test needs to use user configurable functions as was done in
    the prior version. As noted in the VSU user documentation, the X/Open
    specification does not define specific STREAMS devices and modules, hence the
    reason for allowing updates to these in the capi_user functions.
    Test Output
    TEST CASE: readv

    TEST PURPOSE #22
    A call to ssize_t readv(int fildes, const struct iovec
    *iov, int iovcnt) when the function is interrupted by
    a signal after it has successfully read some data
    shall return the number of bytes read.
    PREP: Read IOV_MAX system configuration
    PREP: Allocate and initialize I/O buffers
    PREP: Open and initialize the terminal files
    ERROR: tcgetattr failed, errno = 22(EINVAL - Invalid argument)
    ERROR: Termios_prep failed
    PREP: Open and initialize the terminal files
    ERROR: tcgetattr failed, errno = 22(EINVAL - Invalid argument)
    ERROR: Termios_prep failed
    CLEANUP: Free iovec buffers
    22 UNRESOLVED

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We recommend this request be refused.

    We believe this test is correct as written.

    The XBD states that a pty provides the process with an interface that is
    identical to the terminal subsystem. An implementation which requires
    an application to make additional calls for a pty is not presenting an
    identical interface. The implementation must configure these modules
    (i.e. autopush) in a manner transparent to an application in order to
    be conforming.

    This issue was discussed specifically with the TDG in regards to
    curses testing during test suite development and provisions for
    pushing STREAMS pty modules within the test suite were removed at
    their direction for this reason.

    Also please note that we believe the user modifications to the
    previous version of this test the submitter refers to would have
    been made to routines in capi_com, not capi_user, and thus would
    not have been acceptable for branding purposes.

    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