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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 2534 Actions

    Problem Report Number 2534
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.1310
    Raised 2007-06-27 20:49
    Updated 2007-06-29 00:43
    Published 2007-06-29 00:43
    Product Standard Internationalised System Calls and Libraries Extended V3 (UNIX 03)
    Certification Program The Open Brand certification program
    Test Suite VSX4 version 4.6.7
    Test Identification POSIX.hdr/misc/unistd_X/T.unistd_X 26
    Specification Base Definitions Issue 6
    Location in Spec 14348 in SUSv3 TC2 PDF.
    Problem Summary Test is not required by SUSv3 TC2
    Problem Text According to the current SUSv3 pdf document:

    Constants for Options and Option Groups
    14133 The following symbolic constants, if defined in <unistd.h>, shall
    have a value of &#8722;1, 0, or greater,
    14134 unless otherwise specified below. If these are undefined, the
    fpathconf( ), pathconf( ), or sysconf( )
    14135 functions can be used to determine whether the option is provided
    for a particular invocation of
    14136 the application.
    14137 If a symbolic constant is defined with the value &#8722;1, the option is
    not supported. Headers, data
    14138 types, and function interfaces required only for the option need
    not be supplied. An application
    14139 that attempts to use anything associated only with the option is
    considered to be requiring an
    14140 extension.
    14141 If a symbolic constant is defined with a value greater than zero,
    the option shall always be
    14142 supported when the application is executed. All headers, data
    types, and functions shall be
    14143 present and shall operate as specified.


    and

    14347 _POSIX2_CHAR_TERM
    14348 The implementation supports at least one terminal type.


    I did not see any XBD aardvarks altering this text, so I can't see where
    _POSIX2_CHAR_TERM is required to be 200112L.
    Line 14141 is explicit that a value of 1 is an acceptable value because
    there are no additonal requirements specified
    on line 14348.
    Test Output
    ************************************************************************
    /tset/POSIX.hdr/misc/unistd_X/T.unistd_X 26 Failed

    Test Description:

    For POSIX01 and UNIX03 modes:
    The header file contains a definition for the symbolic constant
    _POSIX2_C_BIND, with the value 200112L, and may contain
    definitions for the symbolic constants _POSIX2_C_DEV,
    _POSIX2_CHAR_TERM, _POSIX2_FORT_DEV, _POSIX2_FORT_RUN,
    _POSIX2_LOCALEDEF, _POSIX2_PBS, _POSIX2_PBS_ACCOUNTING,
    _POSIX2_PBS_CHECKPOINT, _POSIX2_PBS_LOCATE, _POSIX2_PBS_MESSAGE,
    _POSIX2_PBS_TRACK, _POSIX2_SW_DEV and _POSIX2_UPE, each with the
    value -1, 0 or 200112L.
    For UNIX98 mode:
    The header file contains definitions for the symbolic constants
    _POSIX2_C_BIND and _POSIX2_C_VERSION; and, in the case that
    _XOPEN_XCU_VERSION is greater than or equal to 4,
    _POSIX2_CHAR_TERM, _POSIX2_LOCALEDEF and _POSIX2_UPE; which each
    have a value not equal to -1.
    For XPG4 mode:
    If _XOPEN_XCU_VERSION is greater than or equal to 4:
    The header file contains definitions for the symbolic
    constants _POSIX2_C_BIND, _POSIX2_C_VERSION,
    _POSIX2_CHAR_TERM, _POSIX2_LOCALEDEF and _POSIX2_UPE which
    each have a value not equal to -1.

    Test Strategy:
    COMPILE program including <unistd.h>.
    VERIFY symbolic constant exists using #ifndef.
    VERIFY value of constant is as expected.
    VERIFY there were no compiler errors.

    Test Information:
    Feature test macros: -D_XOPEN_SOURCE=600
    Compiler or run-time messages or results:
    _POSIX2_CHAR_TERM is 1, expected -1, 0 or >= 200112
    Feature test macros: -D_XOPEN_SOURCE=600 -D_POSIX_C_SOURCE=200112
    Compiler or run-time messages or results:
    _POSIX2_CHAR_TERM is 1, expected -1, 0 or >= 200112


    ************************************************************************

    Review Information

    Review Type TSMA Review
    Start Date 2007-06-27 20:49
    Last Updated 2007-06-27 23:35
    Completed 2007-06-27 23:35
    Status Complete
    Review Recommendation Test Suite Deficiency (TSD)
    Review Response All of the _POSIX2_* constants have a requirement that the value
    is -1, 0 or 200112L, except _POSIX2_CHAR_TERM. The absence of
    the same requirement for _POSIX2_CHAR_TERM looks like it is
    probably an accidental omission, since there is nothing special
    about _POSIX2_CHAR_TERM that would single it out for being treated
    differently from the other _POSIX2_* constants.

    However, since the standard as published does not state the
    requirement that this test is testing, a test suite deficiency
    should be granted.

    Review Type SA Review
    Start Date 2007-06-27 22:35
    Last Updated 2007-06-28 00:50
    Completed 2007-06-28 00:50
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion A Test Suite deficiency is granted for this PR.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority