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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 2465 Actions

    Problem Report Number 2465
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0670
    Raised 2005-07-12 00:10
    Updated 2005-07-15 18:41
    Published 2005-07-15 18:41
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSC version 5.2.6LT
    Test Identification POSIX.shell/shell 450
    Problem Summary POSIX.shell/shell test 450 should not use awk to test execve() call.
    Problem Text The strategy to use "awk" to test execve() is biased. awk manipulates
    argv[0] and essentially perform a 'argv[0]=basename(argv[0])'. Thus, awk
    statement 'print ARGV[0]' does not print the expected string. Simply
    said, the strategy is testing awk, not execve manipulation of argv[0].
    For comparision purposes, awk perform that operation in netbsd, freebsd
    and gnu. I believe testing execve() argv[0] handling could be
    accomplished by compiling and running this simple C program:

    #include <stdio.h>
    int main(int argc, char *argv[]) {
    printf("%s\n",argv[0]);
    }
    Test Output ********************* FAIL 36
    Assertion #450 (A): When the command name contains slashes, then the
    command is
    Standard output isn't the same as file 'test.450.exp'
    diff of "out.stdout" and "test.450.exp":
    *** out.stdout Wed Jun 22 10:28:52 2005
    --- test.450.exp Wed Jun 22 10:28:52 2005
    ***************
    *** 1 ****
    ! awk
    --- 1 ----
    ! /usr/bin/awk

    Review Information

    Review Type TSMA Review
    Start Date 2005-07-12 00:10
    Last Updated 2005-07-12 18:40
    Completed 2005-07-12 18:40
    Status Complete
    Review Recommendation Rejected (REJ)
    Review Response This test failure is caused by non-conforming behaviour of the awk
    utility on this system. The XCU specification states that the ARGV
    array contains awk's command line arguments (minus the options and
    "program" argument); it does not say that ARGV[0] can contain only the
    last component of the pathname passed as command line argument zero. In
    fact there is no requirement on applications to pass a pathname as
    argument zero - it could contain anything at all, and would be corrupted
    by this awk implementation if it happened to contain one or more '/'
    characters but was not a pathname.

    The fact that this non-conformance of awk has been detected in a test of
    the shell rather than awk itself does not alter the fact that the system
    as a whole is not conforming. (The lack of an equivalent failure in the
    awk tests is noted - this is a deficiency in the awk tests which ought
    to be corrected in a future VSC release.)

    The submitter suggests using a C program in the test instead of
    depending on awk. The dependency on awk is preferable because awk is a
    mandatory utility, whereas development utilities are optional.

    Review Type SA Review
    Start Date 2005-07-12 17:40
    Last Updated 2005-07-13 00:52
    Completed 2005-07-13 00:52
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion The SA does not find that the case has been made that the test is in
    error and thus rejects this PR as a TSD.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority