From: Martijn Dekker <martijn@inlv.org>
To: zsh-workers@zsh.org
Subject: Re: Bug with traps and exit
Date: Sun, 24 Nov 2019 06:54:18 +0100 [thread overview]
Message-ID: <d950fdd8-9c44-b5a4-3b32-dee87dc443f4@inlv.org> (raw)
In-Reply-To: <3859b4bf-08ba-62d5-f00a-3ec4e67caf95@inlv.org>
Op 22-01-19 om 00:00 schreef Martijn Dekker:
> Found a strange issue with traps and 'exit'.
>
> Test script:
>
> trap 'printf $1; exit; printf $2' USR1
> fn() {
> printf 1
> kill -s usr1 $$
> printf 2
> }
> printf 0
> fn A B
> printf 3
>
> Every shell outputs 01A, except zsh, which outputs 01A2.
>
> This means the execution of the fn() function is not interrupted. The
> USR1 trap executes 'exit' and does not execute the rest of the trap
> action, but instead of exiting the shell, zsh continues to execute fn()
> and then exits.
>
> Confirmed down to zsh 5.0.8 (didn't test earlier versions).
A related issue (possibly the same?) with a much simpler test case:
trap 'echo SIGINT; trap - INT; kill -s INT $$; echo woops' INT
kill -s INT $$
zsh prints 'woops', but shouldn't.
- M.
--
modernish -- harness the shell
https://github.com/modernish/modernish
next prev parent reply other threads:[~2019-11-24 22:52 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 7:08 Test release: 5.6.2-test-3 dana
2019-01-05 17:49 ` Peter Stephenson
2019-01-05 18:42 ` dana
2019-01-05 20:58 ` Martijn Dekker
2019-01-05 21:55 ` Daniel Shahaf
2019-01-06 2:37 ` Axel Beckert
2019-01-06 15:12 ` Jun T.
2019-01-06 16:37 ` dana
2019-01-06 16:43 ` Daniel Shahaf
2019-01-06 16:56 ` dana
2019-01-06 21:34 ` Daniel Tameling
2019-01-07 3:25 ` Jun T
2019-01-07 7:02 ` dana
2019-01-21 12:54 ` ETA for zsh 5.7? (was: Test release: 5.6.2-test-3) Axel Beckert
2019-01-21 14:26 ` Peter Stephenson
2019-01-21 19:14 ` Mikael Magnusson
2019-01-21 19:32 ` Mikael Magnusson
2019-01-21 19:32 ` Mikael Magnusson
2019-01-21 21:56 ` Sebastian Gniazdowski
2019-01-22 9:29 ` Peter Stephenson
2019-01-21 23:00 ` Bug with traps and exit Martijn Dekker
2019-11-24 5:54 ` Martijn Dekker [this message]
2019-11-25 16:42 ` Sebastian Gniazdowski
2019-12-10 19:23 ` Martijn Dekker
2019-12-11 2:40 ` Daniel Shahaf
2019-12-12 10:14 ` Peter Stephenson
2019-12-13 14:26 ` Martijn Dekker
2019-12-13 14:49 ` Peter Stephenson
2019-12-14 11:28 ` Daniel Shahaf
2019-12-15 18:59 ` Peter Stephenson
2019-12-16 5:24 ` Daniel Shahaf
2019-12-16 6:37 ` Bart Schaefer
2019-12-17 7:31 ` Daniel Shahaf
2019-12-17 20:29 ` Peter Stephenson
2019-12-18 0:31 ` Daniel Shahaf
2019-12-31 2:03 ` Daniel Shahaf
2019-12-31 13:46 ` Daniel Shahaf
2019-12-16 10:09 ` Peter Stephenson
2019-12-16 5:27 ` The bug from workers/44922 (was: " Daniel Shahaf
2020-01-30 13:49 ` The bug from workers/44922 Martijn Dekker
2020-01-30 14:01 ` Bug with traps and exit Martijn Dekker
2020-01-31 4:29 ` Daniel Shahaf
2022-11-26 3:00 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d950fdd8-9c44-b5a4-3b32-dee87dc443f4@inlv.org \
--to=martijn@inlv.org \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).