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-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.1
X-AuditID: cbfec7f5-f792a6d000001302-25-56efd34eac21
Date: Mon, 21 Mar 2016 10:56:11 +0000
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: segfault in completion for configure
Message-id: <20160321105611.57bf054a@pwslap01u.europe.root.pri>
In-reply-to: <160319190757.ZM28874@torch.brasslantern.com>
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>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFrrILMWRmVeSWpSXmKPExsVy+t/xa7p+l9+HGTz7JmJxsPkhkwOjx6qD
	H5gCGKO4bFJSczLLUov07RK4Mp6/mctScI2lovVLagPjY+YuRk4OCQETia2d91ghbDGJC/fW
	s3UxcnEICSxllPj/8yIrhDODSWLrgc8sEM45RonjC+8xQzhnGSX27P3ECNLPIqAqseD2bjYQ
	m03AUGLqptlgcREBcYmza8+zgNjCQPGHv+eB7eYVsJf4c3M7E4jNKWAlsbRvCjvE0JksEvOm
	bwBr4BfQl7j69xMTxIH2EjOvnGGEaBaU+DH5HlgNs4CWxOZtTawQtrzE5jVvwRYICahL3Li7
	m30Co/AsJC2zkLTMQtKygJF5FaNoamlyQXFSeq6RXnFibnFpXrpecn7uJkZIQH/dwbj0mNUh
	RgEORiUeXoZV78OEWBPLiitzDzFKcDArifDKXAAK8aYkVlalFuXHF5XmpBYfYpTmYFES5525
	632IkEB6YklqdmpqQWoRTJaJg1OqgZFN9fIGvdblwvOyzRLfrYpZln9zgew9Q81sjtifjGXF
	mYbfPl5+uP6/ptLfOcG/7DfOkHGrZ3a7VLftqsH57IPy7rwsyz/2/dS//WstS93id77zfmbk
	bpYPexP+9sOnP+FCERvfbdycFSBVXL739MvGKevV9ngFfmEIup959KFL0e0VN9OLDhUosRRn
	JBpqMRcVJwIAenKIvmQCAAA=
X-Seq: zsh-workers 38195

On Sat, 19 Mar 2016 19:07:57 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> Specifically, if the signals arrive in order USR1 USR2 such that USR2
> is handled during the [[ ]] expression in TRAPUSR1, then the state from
> TRAPUSR2 will be discarded.  I don't know if/how we ought to document.

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?  I don't think
that's an issue.  I'm sure there must be other examples of this.

pws