Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14049
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: [BUG] RETURN trap with -o functrace: infinite recursion on 'eval return' |
| Date | 2018-04-15 22:04 -0400 |
| Organization | ITS, Case Western Reserve University |
| Message-ID | <mailman.12481.1523844277.27995.bug-bash@gnu.org> (permalink) |
| References | <34b02ae0-06b5-0559-a085-efeccc468732@inlv.org> <cafefab8-e34e-e2e0-e6d6-ec9961dfdf66@case.edu> <d1f2983a-454a-9fba-a995-12e162c58eeb@inlv.org> |
On 4/13/18 11:29 PM, Martijn Dekker wrote: > Op 14-04-18 om 03:49 schreef Chet Ramey: >> On 4/10/18 5:56 AM, Martijn Dekker wrote: >>> It seems odd that the RETURN trap would be triggered while a RETURN trap >>> action is still being executed. Might it be better to temporarily >>> deactivate the effect of '-o functrace' while a RETURN trap action is being >>> executed? >> >> Well, trap handlers are recursive, in the sense that you can execute a trap >> on signal X from a signal X trap handler. > > I'm not sure how that would happen. Isn't a signal blocked while executing > its trap handler? No. Since trap handlers are not executed in a signal handler context, there's no reason to block signals while a trap handler is running. Bash doesn't generally allow a trap handler for signal X to run while a trap handler for signal X is executing, but other shells do. This (bash not allowing this trap recursion generally) has been reported as a bug in the past. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: [BUG] RETURN trap with -o functrace: infinite recursion on 'eval return' Chet Ramey <chet.ramey@case.edu> - 2018-04-15 22:04 -0400
csiph-web