|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 1459 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 1459.
Report 1459 Actions
Problem Report Number 1459 Submitter's Classification Test Suite problem State Resolved Resolution Test Suite Deficiency (TSD) Problem Resolution ID TSD.X.0741 Raised 1970-01-01 08:00 Updated 2003-03-13 08:00 Published 1995-11-17 08:00 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 base/ftok 10 11 Problem Summary TSD4U.00073 This test may fail on implementations that detect an invalid id before detecting a non-existent path. Problem Text
This test may fail on implementations that detect an invalid id before
detecting a non-existent path.
The test fails to produce ENOENT because it uses an id field of zero.
According to the SPEC 1170 documentation on ftok():
Only the low-order 8-bits of id are significant. The behavior
of ftok() is unspecified if these bits are zero
Thus I conclude it is wrong to use the following as the basis for
testing ftok(): key = ftok("", 0);
Our implementation returns EINVAL for the above test and since the
behavior is unspecified when id is 0, our behavior is acceptable.
If the 0 in the ftok call is changed to 1 the tests pass.Test Output
10|896 /tset/CAPIbase/fftok/fftok10 17:37:45|TC Start, scenario ref 76-5
15|878 1.10 1|TCM Start
400|878 10 1 17:37:48|IC Start
200|878 1 17:37:48|TP Start
520|878 1 17498144 1 1|SPEC1170TESTSUITE CASE 10
520|878 1 17498144 1 2|ENOENT in errno and return -1 on a call to key_t
520|878 1 17498144 1 3|ftok(const char *path, int id) when path does not
520|878 1 17498144 1 4|exist.
520|878 1 38666264 1 1|PREP: Make sure file does not exist
520|878 1 38666264 1 2|TEST: ENOENT if file doesn't exist
520|878 1 38666264 1 3|ERROR: ftok failed, errno = 121(EINVAL - Invalid
220|878 1 1 17:37:48|FAIL
410|878 10 1 17:37:49|IC End
80|896 0 17:37:49|TC End
10|897 /tset/CAPIbase/fftok/fftok11 17:37:49|TC Start, scenario ref 76-5
15|879 1.10 1|TCM Start
400|879 11 1 17:37:52|IC Start
200|879 1 17:37:52|TP Start
520|879 1 17563680 1 1|SPEC1170TESTSUITE CASE 11
520|879 1 17563680 1 2|ENOENT in errno and return -1 on a call to key_t
520|879 1 17563680 1 3|ftok(const char *path, int id) when path points t
520|879 1 17563680 1 4|empty string.
520|879 1 38731800 1 1|TEST: ENOENT if path points to empty string
520|879 1 38731800 1 2|ERROR: ftok failed, errno = 121(EINVAL - Invalid)
220|879 1 1 17:37:52|FAIL
410|879 11 1 17:37:53|IC End
80|897 0 17:37:53|TC EndReview 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:
- View Report 1459
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority