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

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 2102 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 2102 and all reviews you are authorized to see.

Report 2102 Actions

    Problem Report Number 2102
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.1067
    Raised 1998-06-09 08:00
    Updated 2003-03-13 08:00
    Published 1998-06-11 08:00
    Product Standard Internationalised System Calls and Libraries Extended V2 (UNIX 98)
    Certification Program The Open Brand certification program
    Test Suite VSTH version 5.1.2
    Test Identification PTHR.os/all/pthread_cancel 7
    Linked Problem Reports TSD5TH.00040, (in, old, system)
    Problem Summary TSD5TH.00059 The sem_unlink() setup in pthread_cancel test 7 fails because the setup function sem_unlink_csf() in SRC/common/vsthlib/vsth_cps.c tries to sem_open() on a semaphore named "/var/tmp/<filename>". The "...
    Problem Text

    The sem_unlink() setup in pthread_cancel test 7 fails because the
    setup function sem_unlink_csf() in SRC/common/vsthlib/vsth_cps.c
    tries to sem_open() on a semaphore named "/var/tmp/<filename>".
    The "/var/tmp/<filename>" is created by tmpnam():

    p = tmpnam(Vsth_sem_unlink_buf);
    if ( p == Vsth_sem_unlink_buf )
    {
    Sem_unlink_sem = sem_open(Vsth_sem_unlink_buf, O_CREAT, S_IRWXU, 0);

    Our implementation of tmpnam() always generates a file name using
    a default path prefix of "/var/tmp". XSH5 only says that tmpnam()
    "generates a string that is a valid filename and that is not the same
    as the name of an existing file." XSH5 does not disallow creation of
    this file in an implementation specific directory.

    Using tmpnam() to create a file for use in this test is a problem
    because our implementation of sem_open() requires that the first
    character of name must be a slash (/) character and the remaining
    characters of name not include any slash characters. Thus a filename
    with more than one slash character, such as /var/tmp/<filename>, results
    in the sem_open() function failing with EINVAL.

    XSH5 specifies the following for sem_open():

    "The interpretation of slash characters other than the leading slash
    character in name is implementation-dependent."

    We believe the test is incorrect in its reliance on implementation-dependent
    behavior.

    Test Output

    PTHR.os/all/pthread_cancel/T.pthread_cancel 7
    200|0 7 16:48:00|TP Start
    520|0 7 00007354 1 1|A cancellation point shall not occur when a thread
    520|0 7 00007354 1 2|is executing any of the following C standard or
    520|0 7 00007354 1 3|ISO/IEC 9945-1:1996 functions:
    520|0 7 00007354 1 4|_exit
    520|0 7 00007354 1 5|abort
    520|0 7 00007354 1 6|abs
    520|0 7 00007354 1 7|access
    520|0 7 00007354 1 8|acos
    520|0 7 00007354 1 9|aio_cancel
    520|0 7 00007354 1 10|aio_error
    520|0 7 00007354 1 11|aio_fsync
    520|0 7 00007354 1 12|aio_read
    520|0 7 00007354 1 13|aio_return
    520|0 7 00007354 1 14|aio_write
    520|0 7 00007354 1 15|alarm
    [ non-relevant text deleted ]
    520|1504 7 00009663 412 2|Testing sem_unlink()
    520|1504 7 00009663 412 3|The setup function failed
    520|1504 7 00009663 412 4|sem_unlink() unresolved
    [ non-relevant text deleted ]
    520|0 7 00007354 568 1|wcstombs() passed
    520|0 7 00007354 568 2|Testing wctomb()
    520|0 7 00007354 570 1|wctomb() passed
    220|0 7 2 16:48:01|UNRESOLVED

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    This is an agreed 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