From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2189 invoked from network); 23 Aug 2001 17:51:42 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 23 Aug 2001 17:51:42 -0000 Received: (qmail 19707 invoked by alias); 23 Aug 2001 17:51:35 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15694 Received: (qmail 19695 invoked from network); 23 Aug 2001 17:51:34 -0000 From: Bart Schaefer Message-Id: <1010823175131.ZM25800@candle.brasslantern.com> Date: Thu, 23 Aug 2001 17:51:30 +0000 In-Reply-To: <1010823162607.ZM25653@candle.brasslantern.com> Comments: In reply to Bart Schaefer "Re: seg fault with compstate param" (Aug 23, 4:26pm) References: <3B84D286.B14D2642@yahoo.co.uk> <1010823162607.ZM25653@candle.brasslantern.com> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.dk Subject: Re: seg fault with compstate param MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Aug 23, 4:26pm, Bart Schaefer wrote: } Subject: Re: seg fault with compstate param } } On Aug 23, 10:53am, Oliver Kiddle wrote: } } } } In either 4.0.2 or recentish 4.1 putting the command `typeset compstate' } } in a completion function causes it to seg fault. } } What you did was declare a local variable named compstate that was not an } associative array. That's not quite accurate. The compstate array did retain its special properties when made local. But it was equivalent to `compstate=()', which also causes a core dump. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net