Path: csiph.com!xmission!news.glorb.com!usenet.stanford.edu!not-for-mail From: Chet Ramey Newsgroups: gnu.bash.bug Subject: Re: Script shell suspends after executing second child process Date: Thu, 12 Nov 2015 15:15:27 -0500 Lines: 22 Approved: bug-bash@gnu.org Message-ID: References: Reply-To: chet.ramey@case.edu NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1447359343 5640 208.118.235.17 (12 Nov 2015 20:15:43 GMT) X-Complaints-To: action@cs.stanford.edu Cc: chet.ramey@case.edu To: konsolebox , bug-bash Envelope-to: bug-bash@gnu.org X-Enigmail-Draft-Status: N1110 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 In-Reply-To: X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.5644F362.017A, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2015-08-12 04:07:17, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 02ce68edb75ce42d480c68b2cb6d9574 X-Junkmail-Whitelist: YES (by domain whitelist at mpv3-2015.case.edu) X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.5644F362.02D4,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2015-08-12 04:07:17, dmn=2011-05-27 18:58:46 X-Mirapoint-Loop-Id: e08f18c274e06740f8e3dfb1521a14c8 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 129.22.103.194 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:11872 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 chet@case.edu http://cnswww.cns.cwru.edu/~chet/