|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 1968 Details
Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges
This page provides all information on Problem Report 1968.
Report 1968 Actions
Problem Report Number 1968 Submitter's Classification Test Suite problem State Resolved Resolution Test Suite Deficiency (TSD) Problem Resolution ID TSD.X.0995 Raised 1997-09-10 08:00 Updated 2003-03-13 08:00 Published 1997-09-11 08:00 Product Standard Transport Service XTI Certification Program The Open Brand certification program Test Suite VST version 4.1.4 Test Identification /tset/XTI.os/clts/rcvudata/T.rcvudata 2 Problem Summary TSDT4.033 For test case T.rcvudata 2, the VST4 test suite attempts to verify that a call to t_rcvudata() returns the associated related options specified on the corresponding call to t_sndudata(), after these h... Problem Text
For test case T.rcvudata 2, the VST4 test suite attempts to verify that
a call to t_rcvudata() returns the associated related options specified
on the corresponding call to t_sndudata(), after these have been subject
to negotiation.
This causes an execution loop in findoption() due to the fact that the return
from t_rcvudata() is opt.len = 0 and the contents of the buffer pointed
by opt.buf are not initialised.
Under these conditions, which we believe to be conform to the Spec for
t_rcvudata(), we cannot understand why the test suite is calling findoption()
to analyse the contents of opt.buf . Only the test for a NULL pointer at
the beginning of findoption() could avoid stepping through opt.buf, but
our implementation does not set opt.buf to NULL. Stepping through non-
initialised data could explain various strange behaviour, e.g. looping on
a len=0 first element of an option or addressing outside legal address
space (SIGSEGV) or by chance an "appropriate" len value to leave the while
loop.
Amending VST4 findoption.c to the latest version in VST5 avoids the loop
and test case T.rcvudata 2 gives a pass result. However, it also induces a
regression in the test case T.accept #6, due to a test suite defficiency
in the VST4 accept.c routine getcurropt(), where results from t_optmgmt()
are incompletely returned to the calling test case.
We request that a TSD be accorded to authorise skipping the test case
t_rcvudata #2 by replacing, in the tet_scen file, the line
/tset/XTI.os/clts/rcvudata/T.rcvudata
with the line
/tset/XTI.os/clts/rcvudata/T.rcvudata{1,3-9}
, there by building and executing the remaining 8 test cases.Test Output
Looping in the VST4 findoption() routine for testcase t_rcvudata #2.Review Information
Review Type TSMA Review Start Date null Completed null Status Complete Review Recommendation No Resolution Given Review Response
This is an agreed fault in the test suite and it is recommended that
a waiver is granted on the grounds of a Test Suite Deficiency.
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:
- View Report 1968
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority