|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 0818 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 0818.
Report 0818 Actions
Problem Report Number 0818 Submitter's Classification Test Suite problem State Resolved Resolution Test Suite Deficiency (TSD) Problem Resolution ID TSD.X.0333 Raised 1970-01-01 08:00 Updated 2003-03-13 08:00 Published 1996-04-26 08:00 Product Standard Commands and Utilities V2 (UNIX 95) Certification Program The Open Brand certification program Test Suite VSC version 4.1.5 Test Identification POSIX.cmd/stty 21, 23 Problem Summary TSD4C.00178 This test may fail on implementations that to not support split input/output baud rates. Problem Text
This test may fail on implementations that to not support
split input/output baud rates.
This interpretation request is for the following assertions:
/tset/POSIX.cmd/stty/stty.ex 1 assertion 21
/tset/POSIX.cmd/stty/stty.ex 1 assertion 23
These tests fail on our implementation because we do not support
split baud rates. The XPG4 V2 XSH spec on page 648 states the following:
"... If the terminal device does not support split baud rates, the input
baud rate stored in the termios structure will be 0."
For tp21, check_stty is called, which contains the following code:
if (tcgetattr(0, &tio) < 0) /* orignial termios struct */
.
.
.
.
if (isdigit(argv[1][0])) /* get i_speed and o_speed operand */
{
/* input baud rate should be the same as output baud rate */
ispeed = cfgetispeed(&tio);
ospeed = cfgetospeed(&tio);
if (ospeed == ispeed)
/* Check if the baud stored in termios is the same as
* stty <number> specified, if they are the same,
* return 0; otherwise, return 1
*/
exit(check_speed(ospeed, argv[1]));
else
{
fprintf(stderr, "stty %s setting error\n", argv[1]);
exit(2);
}
}
Since we don't support split baud rates, the cfgetispeed() call will
always set ispeed to zero. The comparision of ispeed and ospeed will
always fail.
For tp23 check_stty ispeed 0 is called and the following code is
executed in check_stty:
case 6:
ispeed = cfgetispeed(&tio);
if (strcmp(argv[2], "0") == 0)
exit(ispeed == cfgetospeed(&tio) ? 0:1);
else
exit(check_speed(ispeed, argv[2]));
ispeed on our implementation will always be 0, so ispeed == cfgetospeed(&tio)
will always evaluate to 0, which causes exit(1) to be executed. This
will cause tp23 to report a failure.
Note, TSD4.248 was granted for VSX, on this problem.Test Output
***********************************************************************
/tset/POSIX.cmd/stty/stty.ex 1 Failed
Test Information:
Assertion #21 (C):
Requested operation failed.
***********************************************************************
***********************************************************************
/tset/POSIX.cmd/stty/stty.ex 1 Failed
Test Information:
Assertion #23 (C):
Command failed: 'check_stty ispeed 0'
***********************************************************************
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:
- View Report 0818
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority