Re: lib/52517: TTY settings modified and not restored on exit.

[christos%zoulas.com@localhost (Christos Zoulas)]

On Aug 31,  9:50pm, jhdub23%gmail.com@localhost (jhdub23%gmail.com@localhost) wrote:
-- Subject: lib/52517: TTY settings modified and not restored on exit.

| >Number:         52517
| >Category:       lib
| >Synopsis:       TTY settings modified and not restored on exit.
| >Confidential:   no
| >Severity:       non-critical
| >Priority:       medium
| >Responsible:    lib-bug-people
| >State:          open
| >Class:          sw-bug
| >Submitter-Id:   net
| >Arrival-Date:   Thu Aug 31 21:50:00 +0000 2017
| >Originator:     Jay West
| >Release:        libedit (NetBSD-current)
| >Organization:
| Self
| >Environment:
| Linux [deleted] 2.6.32-696.6.3.el6.x86_64 #1 SMP Wed Jul 12 14:17:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
| >Description:
| libedit modifies TTY settings when used, and does not have a mechanism to fully save and restore TTY settings.  This causes problems when libedit is used as a GNU readline replacement.
| 
| Specifically, after running python+GnuReadline, TTY settings are untouched after python exits.  However, python+libedit has noticeable TTY changes after python exits.
| 
| This will be true for any application linked against libedit instead of GnuReadline.
| >How-To-Repeat:
| % stty -a > orig.txt
| % python # Run python compiled with libedit, and immediately exit (or any application using libedit).
| % stty -a > after.txt
| % diff orig.txt after.txt  # Differences exist
| 


Can you provide a small program that calls readline and reproduces this?

christos