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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1783 Actions

    Problem Report Number 1783
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0860
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1999-05-10 08:00
    Product Standard Window System Application Interface V2
    Certification Program The Open Brand certification program
    Test Suite VSW version 5.0.2
    Test Identification Xproto/NoOperation 3
    Problem Summary TSD4W.00166 This test may fail because an undefined big request length of 0 is being sent rather than 1.
    Problem Text
    VSW Protocol tests use zero for the request length when
    they want to send a BadLength request.

    However, using zero for request length when BigRequests
    is turned on means that the current request is a big one and
    the length is in the next four bytes after the request.
    (Notice the INFO statement "Processing a big request")

    The test suite then erroneously puts zero as the big request length.
    BigRequest lengths should be specified as desired request length
    *plus* one for the extra long.

    The test suite should put one (1) in the big request length
    if they want zero (0) to be the actual request length.

    The reason that all the other protocol tests fail with a
    BadLength error and NoOp doesn't is that when the server
    subtracts one (1) from the Big Request length (0) it gets
    a request length of 0xffffffff which is a legal NoOp request
    length and is BadLength for the rest of the protocol.

    Test Output
    520|75 3 00004129 1 1|VSW5TESTSUITE PURPOSE 3
    520|75 3 00004129 1 2|Assertion NoOperation-3.(A)
    520|75 3 00004129 1 3|When a client sends an invalid NoOperation protocol request
    520|75 3 00004129 1 4|to the X server, in which the length field of the request is
    520|75 3 00004129 1 5|less than the minimum length required to contain the
    520|75 3 00004129 1 6|request, then the X server sends back a BadLength error to
    520|75 3 00004129 1 7|the client.
    520|75 3 00004129 1 8|METH: Call library function testfunc() to do the following:
    520|75 3 00004129 1 9|METH: Open a connection to the X server using native byte sex.
    520|75 3 00004129 1 10|METH: Send an invalid NoOperation protocol request to the X server with length
    520|75 3 00004129 1 11|METH: one less than the minimum length required to contain the request.
    520|75 3 00004129 1 12|METH: Verify that the X server sends back a BadLength error.
    520|75 3 00004129 1 13|METH: Open a connection to the X server using reversed byte sex.
    520|75 3 00004129 1 14|METH: Send an invalid NoOperation protocol request to the X server with length
    520|75 3 00004129 1 15|METH: one less than the minimum length required to contain the request.
    520|75 3 00004129 1 16|METH: Verify that the X server sends back a BadLength error.
    520|75 3 00004153 1 1|INFO: Processing a big request
    520|75 3 00004153 1 2|REPORT: Expect: wanted ERROR - BadLength , got NOTHING
    520|75 3 00004153 1 3|REPORT: client 0 failed to recv BadLength error
    520|75 3 00004153 1 4|REPORT: Test NoOperation failed with 1 error.
    520|75 3 00004156 1 1|INFO: Processing a big request
    520|75 3 00004156 1 2|REPORT: Expect: wanted ERROR - BadLength , got NOTHING
    520|75 3 00004156 1 3|REPORT: client 0 failed to recv BadLength error
    520|75 3 00004156 1 4|REPORT: Test NoOperation failed with 1 error.
    220|75 3 1 13:30:29|FAIL
    410|75 3 1 13:30:29|IC End

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We agree this is a test suite deficiency in the test
    suite version(s) listed.

    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