Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #11872 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2015-11-12 15:15 -0500 |
| Last post | 2015-11-12 15:15 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Script shell suspends after executing second child process Chet Ramey <chet.ramey@case.edu> - 2015-11-12 15:15 -0500
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2015-11-12 15:15 -0500 |
| Subject | Re: Script shell suspends after executing second child process |
| Message-ID | <mailman.2198.1447359342.7904.bug-bash@gnu.org> |
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/
Back to top | Article view | gnu.bash.bug
csiph-web