From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24401 invoked by alias); 21 Apr 2017 22:18:56 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 40997 Received: (qmail 27012 invoked from network); 21 Apr 2017 22:18:56 -0000 X-Qmail-Scanner-Diagnostics: from mail-vk0-f42.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.213.42):SA:0(0.5/5.0):. Processed in 1.357266 secs); 21 Apr 2017 22:18:56 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=0.5 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RCVD_IN_SORBS_SPAM,SPF_PASS, T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.213.42 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=wyFJThKwWuqZkm2IAzwgCwrXE3oTu/+3Y6mYW3fE5uQ=; b=2Ni6Amkjp5dnQiui02nqtsxColAQBWp0n5Nr4yl8vX0Io9Jsq4DjZhWWhXTUCBaxwC Nouedw61YG3qYJMW53vOT3Skxte1V7CV1G64yahD7GcqSoppTnsyxl6cE3FNndxVZfWw k35XIdwaeD0gi1jh/soIsHz6hOXWgzNLxwyzfx5fL8pjrtkm0DhEoCnQ9iiXaYHeqknG MbJB/UKfEzOInQAOwwVrnABhWUxJNiSFVw9Yhkz96Fmoasvtdq5HZ2lnCIrD7XV1z8a9 cn86o+ES9A2MG+qzN0FPkVPRiMpzD9awb4k9TZ2FH0sLwEkBYfLGhEnkLjte5jegS096 nHSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=wyFJThKwWuqZkm2IAzwgCwrXE3oTu/+3Y6mYW3fE5uQ=; b=Flr6g9KMhU54WkMB0dA9wTQi75KRdz6GS9x+G04N0bqBOvZmJuO5CG8zkEvIt/kB3D C1ZjSHHSSsvJXaJk1pTJyAB6W9pz8/grVwAjRfqBrntIm6fqxQ27f6nc63tnHAQWOojg o257iGi496blze/Ui18c1umvuhe4Uy1Wi+emgXb/mZ6MHM8B+y9gnQvJvDV20Cgb5rZi TTUjM1eJf1HrzTyoxqM5nxz18uh7H30cfKd3AnZNntWTLX2EaF5lTR7uFMtRsgPqVfIu szmYZhH7KhDGNqRxebu03D8P66pQdN21cn1Vv3m18RCAni34WN5rUexlL2Ij2rXY5pTW gXpg== X-Gm-Message-State: AN3rC/6Lk1gYP/9Yt3uXBddSpgCfWu9CwgWgEZkm+RGoFKQPhkdb5y3q GBMVkSlswGM/dXd7 X-Received: by 10.31.14.194 with SMTP id 185mr5664644vko.176.1492813127678; Fri, 21 Apr 2017 15:18:47 -0700 (PDT) From: Bart Schaefer Message-Id: <170421151904.ZM7627@torch.brasslantern.com> Date: Fri, 21 Apr 2017 15:19:04 -0700 In-Reply-To: <87efwlijrl.fsf@wirrsal.net> Comments: In reply to Sebastian Reusse "Call stack issues when running trap handler" (Apr 21, 10:32pm) References: <87efwlijrl.fsf@wirrsal.net> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Call stack issues when running trap handler MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 21, 10:32pm, Sebastian Reusse wrote: } } I've noticed that under certain conditions, shell functions called from } inside an exit trap handler appear to never return. Whatever this is dates back a long time. In zsh-3, the sample script doesn't appear to call the exit trap at all via "main" or "exit0" though it does if "exit" is called directly. In zsh-4 the behavior is the same as in current zsh-5.