On 11/12/15 5:27 AM, konsolebox wrote:
> My interactive (using `read`) Bash-script application still suspends
> itself after
> executing second instance of a player. I've only seen this happen in
> the newest development version of Bash.
You should be able to attach to the stopped process with gdb and get a
stack traceback, at least to the point where it's clear whether it's
stopping on an attempt to set the terminal attributes or on a read().
According to the change log, the last time I made a change that might
be relevant to this problem was April 23. You might try getting the
version immediately preceding that one and seeing whether or not that
version has the problem.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
