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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1186 Actions

    Problem Report Number 1186
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0388
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Sockets (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSU version 4.1.0
    Test Identification sockets/getprotoent 5
    Problem Summary PG4U.00079 This test claims that a setprotoent() call is required to initialize the database before getprotoent() is used.
    Problem Text
    We believe this is a test suite deficiency.

    The only other test purpose that is executed for this function is
    test purpose #1. It first calls setprotoent(1) to rewind the database
    before the first call to getprotoent().

    When test purpose #5 is executed the database is at end-of-file since
    the last use of the database was in test purpose #1. No call is made
    to setprotoent(1) in test purpose #5, so the database is never rewound.
    Therefore, the first call to getprotoent() fails because it is already
    at end-of-file. When I add a call to setprotoent() to test purpose #5,
    just before the first call to getprotoent(), this test case passes.
    Test Output
    TEST CASE: getprotoent

    TEST PURPOSE #5
    Return a null pointer on a call to struct protoent
    *getprotoent(void) when the end of the network
    protocol database was reached.
    PREP: Call getprotoent() the number of times defined by
    the configuration variable VSU_PROTO_CNT
    ERROR: getprotoent failed on call 1
    5 FAIL

    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 the test is correct.

    Each test is executed as a separate process via the capi_com execute()
    function. Since the parent process does not reference these
    functions, connections to the database are not inherited between
    tests. As a result, each test must open a new connection in order to
    access the database.

    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