Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: The bug from workers/44922

X-seq: zsh-workers 45360
From: Martijn Dekker <martijn@xxxxxxxx>
To: zsh-workers@xxxxxxx
Subject: Re: The bug from workers/44922
Date: Thu, 30 Jan 2020 14:49:18 +0100
In-reply-to: <20191216052713.zuhf22nqzgdjz4z4@tarpaulin.shahaf.local2>
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
References: <3859b4bf-08ba-62d5-f00a-3ec4e67caf95@inlv.org> <d950fdd8-9c44-b5a4-3b32-dee87dc443f4@inlv.org> <20191216052713.zuhf22nqzgdjz4z4@tarpaulin.shahaf.local2>

Op 16-12-19 om 06:27 schreef Daniel Shahaf:

Martijn Dekker wrote on Sun, Nov 24, 2019 at 06:54:18 +0100:

[...]

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.


As Peter observed in 45037, could you elaborate on why the inner 'kill' should
abort execution of the trap?

I can't see much to elaborate on. After unsetting a trap, a signalshould revert to its default action, which in this case is "abnormaltermination" (i.e. termination with a > 128 exit status specifying thesignal). The fact that all this happens within a trap action should notmake any difference.


- Martijn

--
modernish -- harness the shell
https://github.com/modernish/modernish

Messages sorted by: Reverse Date, Date, Thread, Author