libs/newlib-cygwin
libs
/
newlib-cygwin
mirror of git://sourceware.org/git/newlib-cygwin.git
4
0
Fork 0
Code Issues Projects Releases Wiki Activity
newlib-cygwin/winsup/cygwin/release/3.1.5

15 lines
583 B
Groff
Raw Normal View History

Cygwin: add release message for NUL character bugs Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2020-02-21 17:57:10 +08:00
Bug Fixes:
----------
- Fix accidental evaluation of NUL (\0) characters in xterm console output.
Don't move cursor to the right in case of a NUL character in the console
output stream, this is not backed by terminfo.
Addresses: https://cygwin.com/ml/cygwin/2020-02/msg00162.html
Cygwin: console: Fix segfault on shared_console_info access. - Accessing shared_console_info before initialization causes access violation because it is a NULL pointer. The cause of the problem reported in https://cygwin.com/ml/cygwin/2020-02/msg00197.html is this NULL pointer access in request_xterm_mode_output() when it is called from close(). This patch makes sure that shared_console_info is not NULL before calling request_xterm_mode_output().
2020-02-25 00:12:16 +08:00
- Fix a segfault when starting, e.g., mintty from a bash in a console
running xterm emulation.
Addresses: https://cygwin.com/ml/cygwin/2020-02/msg00197.html
Cygwin: ioctl: TIOCINQ: always return number of chars in the inbound queue So far ioctl(TIOCINQ) could end up returning -1 with errno set to EINVAL if a non-zero device error mask has been returned by ClearCommError. This doesn't reflect Linux behaviour, which always returns the number of chars in the inbound queue, independent of any I/O error condition. EINVAL was a pretty weird error code to use in this scenario, too. Fix this by dropping all checking for device errors in the TIOCINQ case. Just return the number of chars in the inbound queue. Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2020-03-03 00:02:51 +08:00
- Fix TIOCINQ to always return number of inbound chars if available.
Addresses: https://cygwin.com/ml/cygwin/2020-02/msg00258.html