Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160321082611.ZM25776@torch.brasslantern.com>
Date: Mon, 21 Mar 2016 08:26:11 -0700
In-Reply-To: <20160321105611.57bf054a@pwslap01u.europe.root.pri>
Comments: In reply to Peter Stephenson <p.stephenson@samsung.com>
        "Re: segfault in completion for configure" (Mar 21, 10:56am)
References: <20160311134729.GA32476@cventin.lip.ens-lyon.fr> 
	<20160311143202.4008e29b@pwslap01u.europe.root.pri> 
	<160311150056.ZM30997@torch.brasslantern.com> 
	<20160312031116.GC28459@zira.vinc17.org> 
	<160312082029.ZM2340@torch.brasslantern.com> 
	<160312093420.ZM14020@torch.brasslantern.com> 
	<20160313215831.GA23404@zira.vinc17.org> 
	<160314194323.ZM6887@torch.brasslantern.com> 
	<20160317152435.GC11303@cventin.lip.ens-lyon.fr> 
	<160317111515.ZM16697@torch.brasslantern.com> 
	<160319190757.ZM28874@torch.brasslantern.com> 
	<20160321105611.57bf054a@pwslap01u.europe.root.pri>
To: zsh-workers@zsh.org
Subject: Re: segfault in completion for configure
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Mar 21, 10:56am, Peter Stephenson wrote:
}
} Are you simply worried that a pattern match that happens
} asynchronously might not leave behind $MATCH / $match etc. values
} after return owing to other asynchronous goings on with pattern
} matching?

The point is that a pattern match that happens asynchronously might not
leave behind $MATCH / $match etc. values owing to other pattern matches
going on, period, whether synchronous or async.  Two signal handlers in
the example was just to set up a way to get into the situation; a glob
that takes several seconds to complete might just as easily do it, but
is hard to invent for purposes of example code.

I'm the tiniest bit worried that there's a way $MATCH et al. might be
left pointing at garbage memory, but I don't really think so.

} I don't think that's an issue.

I don't think it's an issue either, but it's going to do the potentially
unexpected thing more consistently now, so I wondered if it should be
documented.