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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1171 Actions

    Problem Report Number 1171
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0373
    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.0
    Test Identification CAPIbase/getutxent 1
    Problem Summary PG4U.00095 This was refused because it is a duplicate. Use TSD4U.00136 instead.
    Problem Text
    Test cases: base/getutxent1

    Sometimes this test case fails with a different result though
    the cause is the same as reported in TSD4U.00136.
    A negative number is produced by using the time in seconds
    value. This differs from execution to execution and apparently
    on some executions when the value produced is massaged into a
    unique number and converted to character a different result
    occurs and possibly some unprintable characters make their way into
    the ut_id array, followed by the NULL character. The appearance
    of this particular result is unpredictable and I can't seem to
    reproduce it today but it does crop up from time to time so
    I wanted to be sure to cover our bases on this.
    As the journal run shows, the ut_id is empty but the failure here
    is different. Either a different millesecond value caused a
    different id string or a utmpx database was different during this
    particular execution and that led to a different result.
    I cannot figure out what happened here without extremely detailed
    analysis although it is a sure thing that an overflow is occuring
    when the ut_id is being generated, and that a successful run will
    never be possible.
    The syscall matches on the ut_id field even though there are
    apparently several records in the database with that "empty"
    id. Thus there are multiple records with duplicate ids.
    This explains the failure to get the correct time.
    Test Output
    10|681 /tset/CAPIbase/fgetutxent/fgetutxent1 14:16:38|TC Start, scenario
    15|681 1.10 1|TCM Start
    400|681 1 1 14:16:45|IC Start
    200|681 1 14:16:45|TP Start
    520|681 1 149618748 1 1|SPEC1170TESTSUITE CASE 1
    520|681 1 149618748 1 2|A successful call to struct utmpx
    520|681 1 149618748 1 3|*getutxent(void) shall read the next entry from
    520|681 1 149618748 1 4|user accounting database and return a pointer to
    520|681 1 149618748 1 5|structure containing a copy of the entry.
    520|681 1 264306756 1 1|PREP: Find a unique ut_id for use by the test
    520|681 1 264306756 1 2|PREP: Compute the number of entries in the user
    520|681 1 264306756 1 3|PREP: Initialize a unique database entry
    520|681 1 264306756 1 4|PREP: rewind the database
    520|681 1 264306756 1 5|PREP: Write the entry to the database
    520|681 1 264306756 1 6|PREP: Initialize a unique database entry
    520|681 1 264306756 1 7|PREP: rewind the database
    520|681 1 264306756 1 8|PREP: Write the entry to the database
    520|681 1 264306756 1 9|PREP: Initialize a unique database entry
    520|681 1 264306756 1 10|PREP: rewind the database
    520|681 1 264306756 1 11|PREP: Write the entry to the database
    520|681 1 264306756 1 12|PREP: rewind the database
    520|681 1 264306756 1 13|PREP: Seek to the location in the utmp database
    520|681 1 264306756 1 14| the new entries should be
    520|681 1 264306756 1 15|TEST: getutxent() reads next entry from utmp database
    520|681 1 264306756 1 16|ERROR: Invalid entry obtained from the database
    520|681 1 264306756 1 17| Expected entry: Type=6 Timestamp=sec:839701007
    520|681 1 264306756 1 18| Id= User=VSU0 Pid=264306756 Li
    520|681 1 264306756 1 19| Got entry: Type=6 Timestamp=sec:839701008 msec
    520|681 1 264306756 1 20| Id= User=VSU0 Pid=264306756 Li
    220|681 1 1 14:16:48|FAIL
    410|681 1 1 14:16:48|IC End
    80|681 0 14:16:48|TC End

    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.

    The submitter is correct but a recent ruling regarding this issue
    exists. To avoid the confusion duplicate rulings regarding the same
    issue might cause we recommend this request be refused and the submitter
    use TSD4U.00136 instead.

    We have added the test results shown here to the results presented
    in TSD4U.00136.

    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