From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-27318-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 26834 invoked by alias); 30 Oct 2009 21:21:39 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 27318
Received: (qmail 11225 invoked from network); 30 Oct 2009 21:21:37 -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-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 209.85.218.210 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type;
        bh=xvdSiQr/MdG3mAYsC3irEu+3PeyBzhrP5JFxRotZgDY=;
        b=M9NzEhAwUJGoARfhdpRRntWLvSlzgxyJucOouca2iI9vJZHKzj603aknJ3QzcZsM6s
         wy8ruD/smMavtx7CjHQsxsAmzdEaVyX8fNtg1GLysg65BJ/IzMFhaTIGYO459+yvpgQe
         RtG9Wb2JRykYVEzZS9ImT6LS7u1Qnby66sQbI=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=t8CoG3/VJW/VPnlREONth7WcE/wjGJeRuUdZsFcL0ozwngXR0+FIF83rmEd6oduyV6
         rErXWGG+ZHuFndZ82fnEPDQ8X7Pt5EU75gMNYEDmQ3f0m6Q5+bBwZbWxZcTjCig1qkFP
         5P2P9xDuVFyz4xFTONYzg8MayvAiZBKtRsx+k=
MIME-Version: 1.0
In-Reply-To: <20091030161027.GL3082@fsst.voodoo.lan>
References: <20091030161027.GL3082@fsst.voodoo.lan>
Date: Fri, 30 Oct 2009 22:14:29 +0100
Message-ID: <237967ef0910301414w7c051308m62c5227f30b74ada@mail.gmail.com>
Subject: Re: zsh eats 100% CPU with completion in /
From: Mikael Magnusson <mikachu@gmail.com>
To: zsh-workers@zsh.org
Content-Type: text/plain; charset=UTF-8

2009/10/30 Frank Terbeck <ft@bewatermyfriend.org>:
> The subject is not entirely correct.
>
> Zsh eats 100% CPU on a colleague's laptop if you do this:
> % cd /
> % cd ..
> % ./<tab>
>
> Happens with the most recent CVS HEAD, too.
> That's on linux (debian stable, actually).
>
> The problem is reproducible on his machine. And it doesn't happen if
> you do this:
> % cd /
> % ./<tab>
>
> The 'cd ..' is required.
>
> I cannot reproduce the problem on my system with exactly the same
> configuration and with exactly the same zsh version. And I am in fact
> using the very same OS (debian stable), too.
>
> As you can imagine, I am quite puzzled and I don't know how to tackle
> this.
>
> Any hints or suggestions are highly welcome.

I can reproduce this, but not under gdb, and, curiously, not if I
first start another instance of zsh, ie:
%(1) zsh
%(2) cd /
%(2) cd ..
%(2) <tab> -> produces listing
%(2) exit
%(1) cd /
%(1) cd ..
%(1) <tab> -> hangs

Here's a backtrace without debug symbols while i rebuild:
#0  0x080d5cc0 in itype_end ()
#1  0x6fafd51f in docomplete () from /usr/local/lib/zsh/4.3.10-dev-1/zsh/zle.so
#2  0x6faf91d0 in completecall () from
/usr/local/lib/zsh/4.3.10-dev-1/zsh/zle.so
#3  0x6fae935d in execzlefunc () from /usr/local/lib/zsh/4.3.10-dev-1/zsh/zle.so
#4  0x6fae9582 in zlecore () from /usr/local/lib/zsh/4.3.10-dev-1/zsh/zle.so
#5  0x6fae9b89 in zleread () from /usr/local/lib/zsh/4.3.10-dev-1/zsh/zle.so
#6  0x6faebbf7 in zle_main_entry () from
/usr/local/lib/zsh/4.3.10-dev-1/zsh/zle.so
#7  0x08083df0 in zleentry ()
#8  0x08087a53 in inputline ()
#9  0x08087c88 in ingetc ()
#10 0x08082958 in ihgetc ()
#11 0x08090fc6 in zshlex ()
#12 0x080b30aa in parse_event ()
#13 0x08085004 in loop ()
#14 0x08086f2e in zsh_main ()
#15 0x080554b2 in main ()


-- 
Mikael Magnusson