[lsb-bugs] [Bug 3033] New: T.c_iflag and T.tcgetattr fail when using pseudo ttys

bugzilla-daemon at linux-foundation.org bugzilla-daemon at linux-foundation.org
Wed Sep 1 11:55:14 PDT 2010


http://bugs.linuxbase.org/show_bug.cgi?id=3033

           Summary: T.c_iflag and T.tcgetattr fail when using pseudo ttys
           Product: Distribution Tests
           Version: 4.0
          Platform: All
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: lsb-test-core
        AssignedTo: stewb at linux-foundation.org
        ReportedBy: brett.pub at gmail.com
         QAContact: lsb-bugs at freestandards.org


/tset/POSIX.os/devclass/c_iflag/T.c_iflag 6     Failed
     read() returned 1, expected 0
/tset/POSIX.os/devclass/c_iflag/T.c_iflag 7     Failed
     read() returned 1, expected 3
     when ISTRIP flag was clear
     read() returned 1, expected 3
     when ISTRIP flag was set
/tset/POSIX.os/devclass/c_iflag/T.c_iflag 8     Failed
     read 0377, expected 0
/tset/POSIX.os/devclass/c_iflag/T.c_iflag 9     Failed
     read 0377, expected 0

All four of these suggest bugs with tty parity handling.
I looked for parity checking on pseudo-ttys and could not find
any; that is probably where the problem is.

/tset/POSIX.os/devclass/tcgetattr/T.tcgetattr 1 Failed
/tset/POSIX.os/devclass/tcgetattr/T.tcgetattr 2 Failed

These appear to be similar: the test tries to set CS7 and PARENB
on a pseudo-tty, which refuses to take those (stays at CS8, no
parity) and then the test fails because the tty is set to 8-bits-no-parity
instead of 7-bits-even-parity.

============
Related to:
### Problem Record #58 TESTSUITE core TEST
/tset/POSIX.os/devclass/c_iflag/T.c_iflag 19   SEVERITY warning    MARKER This
test will not pass when using pseudo ttys COMMENT This is a normal result
unless a hardware terminal is used (which is very rare). RESOLUTION Normal
WAIVE  END

-- 
Configure bugmail: http://bugs.linuxbase.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the lsb-bugs mailing list