From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12471 invoked from network); 3 Jan 2005 15:59:01 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 3 Jan 2005 15:59:01 -0000 Received: (qmail 84346 invoked from network); 3 Jan 2005 15:58:54 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 3 Jan 2005 15:58:54 -0000 Received: (qmail 22392 invoked by alias); 3 Jan 2005 15:58:40 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 20642 Received: (qmail 22375 invoked from network); 3 Jan 2005 15:58:39 -0000 Received: from unknown (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 3 Jan 2005 15:58:39 -0000 Received: (qmail 83540 invoked from network); 3 Jan 2005 15:57:39 -0000 Received: from moonbase.zanshin.com (64.84.47.139) by a.mx.sunsite.dk with SMTP; 3 Jan 2005 15:57:36 -0000 Received: from toltec.zanshin.com (toltec.zanshin.com [64.84.47.166]) by moonbase.zanshin.com (8.13.1/8.13.1) with ESMTP id j03FvXBJ009411 for ; Mon, 3 Jan 2005 07:57:33 -0800 Date: Mon, 3 Jan 2005 07:57:33 -0800 (PST) From: Bart Schaefer Reply-To: zsh-workers@sunsite.dk To: zsh-workers@sunsite.dk Subject: Re: Zsh killed when autoloaded function calls mislinked program In-Reply-To: <200412211130.iBLBUV9D011813@news01.csr.com> Message-ID: References: <20041220202059.GE11940@alan.cs.pdx.edu> <200412211130.iBLBUV9D011813@news01.csr.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checker-Version: SpamAssassin 2.63 on a.mx.sunsite.dk X-Spam-Level: X-Spam-Status: No, hits=0.0 required=6.0 tests=none autolearn=no version=2.63 X-Spam-Hits: 0.0 [I'm back from holiday travel.] On Tue, 21 Dec 2004, Peter Stephenson wrote: > - killjb(jn, lastval & ~0200); > + if (jn->gleader) > + killjb(jn, lastval & ~0200); This looks right to me, but I haven't groveled through that code for a while. The only case where it might be wrong is in a subshell if the subshell is to die with the same signal as the job, but I *think* that's handled elsewhere by the value passed to exit() ... and AFAICT from some attempts at testing, it is.