Re: [Bug-readline] terminal corruption with spawned ruby processes

[Chet Ramey]

On 4/12/17 12:38 PM, Eric Thompson wrote:
> 
> 
> On Tue, Apr 11, 2017 at 6:43 PM, Chet Ramey <address@hidden
> <mailto:address@hidden>> wrote:
> 
>     On 4/11/17 5:22 PM, Eric Thompson wrote:
>     > Hi all,
>     >    I ran into a possible problem in readline developing a library for 
> Rake
>     > to aid in managing and launching processes.
>     >
>     > basically, if you use (ruby) Process.spawn or other ways to launch a
>     > subprocess that don't detach and that process inherits the stdin default
>     > pipe of the parent, the terminal input gets corrupted before hitting the
>     > child process (if that child is using readline).
> 
>     All indications are that you have multiple processes simultaneously
>     attempting to read from stdin.
> 
> 
> maybe.  that's not how ruby Process is supposed to work.  in addition, this
> isn't an issue when using alternatives to gnu readline (editline, 
> rb-readline).

A system call tracer would show how many processes were trying to read
from the same file descriptor, in addition to showing whether or not this
is due to some signal handling issue.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/