From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26825 invoked from network); 30 Oct 2008 21:26:34 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 30 Oct 2008 21:26:34 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 20887 invoked from network); 30 Oct 2008 21:26:29 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 30 Oct 2008 21:26:29 -0000 Received: (qmail 25407 invoked by alias); 30 Oct 2008 21:26:21 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 25974 Received: (qmail 25388 invoked from network); 30 Oct 2008 21:26:19 -0000 Received: from bifrost.dotsrc.org (130.225.254.106) by sunsite.dk with SMTP; 30 Oct 2008 21:26:19 -0000 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by bifrost.dotsrc.org (Postfix) with ESMTP id 4F6BB80524C0 for ; Thu, 30 Oct 2008 22:26:14 +0100 (CET) Received: by wa-out-1112.google.com with SMTP id m28so466902wag.29 for ; Thu, 30 Oct 2008 14:26:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=M8ZP8yzKJtbOpoydE78RC7S7pQPqyCAl5wPLRtbsDr0=; b=tzBmyyL/ErxmF+uXWaRZuf+2jToGPEhgIW9oPwRSH4Skkk3noXuOVSxzaodGhlig/a ITivaBeNUKOE4RAFgkAD0vohhLyDQEXyqxYKchyLvYd3LybPbwqDJSE9L+UIfS+4yXY9 +Dx9+5gcywBlfX+bT7hbxYGJhcWUnAno5IqiU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=jVFIqf1JZQu5hMBWgq9fnaxe6TlI5+Q4kVpYl7cM0F9VYo4FnsPjjI3p53KhiEVlvw O2amqQfVBFNvtkFWgJMUPeVEr02MGnQOpQXraanaBukfGBTlARSvxHQQ/8MGM/cZQNUr uhitS0EQNjaCeClZRI9i8Pq0A1Hyc993jtP9Q= Received: by 10.114.182.1 with SMTP id e1mr9197260waf.143.1225401972030; Thu, 30 Oct 2008 14:26:12 -0700 (PDT) Received: by 10.114.112.17 with HTTP; Thu, 30 Oct 2008 14:26:11 -0700 (PDT) Message-ID: <237967ef0810301426l1d2b0698xd58eea08a01eb4b0@mail.gmail.com> Date: Thu, 30 Oct 2008 22:26:11 +0100 From: "Mikael Magnusson" To: "Oliver Kiddle" Subject: Re: another bug: zsh_directory_name Cc: "Zsh workers" In-Reply-To: <20324.1225401654@thecus> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20324.1225401654@thecus> X-Virus-Scanned: ClamAV 0.92.1/8544/Thu Oct 30 19:59:19 2008 on bifrost X-Virus-Status: Clean 2008/10/30 Oliver Kiddle : > Just thought I'd check that the case of calling this new ~[...] stuff > recursively had been handled. The following caused an instant seg fault: > > zsh_directory_name() { > echo ~[] > } I don't think this has anything to do with ~[], % function a() { a } % a zsh: segmentation fault zsh (i appear to not have debug symbols but maybe better than nothing), (gdb) bt #0 0x08069b4c in execcmd () #1 0x0806df95 in execpline2 () #2 0x0806e39d in execpline () #3 0x00000000 in ?? () -- Mikael Magnusson