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-f79b16d000005389-a2-56e2d6e5bb45
Date: Fri, 11 Mar 2016 14:32:02 +0000
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: segfault in completion for configure
Message-id: <20160311143202.4008e29b@pwslap01u.europe.root.pri>
In-reply-to: <20160311134729.GA32476@cventin.lip.ens-lyon.fr>
References: <20160311134729.GA32476@cventin.lip.ens-lyon.fr>
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+NgFjrHLMWRmVeSWpSXmKPExsVy+t/xq7pPrz0KM+jtYLM42PyQyYHRY9XB
	D0wBjFFcNimpOZllqUX6dglcGae7nAqmcFTceBrUwHiWrYuRk0NCwERi2aR9ULaYxIV764Fs
	Lg4hgaWMEruPbWWEcGYwSTS/+wblnGOUuH/xLSuEc5ZR4sD9Ncwg/SwCqhLH1/aC2WwChhJT
	N81mBLFFBMQlzq49zwJiCwPFH/6eB1bDK2AvMefHLKBBHBycArYSLU88QMJCAjYSp5o3sYPY
	/AL6Elf/fmKCOM9eYuaVM4wQrYISPybfAxvJLKAlsXlbEyuELS+xec1bZog56hI37u5mn8Ao
	PAtJyywkLbOQtCxgZF7FKJpamlxQnJSea6RXnJhbXJqXrpecn7uJERLKX3cwLj1mdYhRgINR
	iYf3w7WHYUKsiWXFlbmHGCU4mJVEeJdcfRQmxJuSWFmVWpQfX1Sak1p8iFGag0VJnHfmrvch
	QgLpiSWp2ampBalFMFkmDk6pBsZkJz6bOzEGxt5FQp5P66b23lj0dnt+0o3mBebbm46UTF7h
	cbhAKqzN7v7HwnKjhztO8dXOdVxa/eXAn+w/W71Cn8QkfdQ225DHdUbq9i3Vm3WPmwwWOOR/
	ZTuaf62QideSd1V0kueEQ6rCi+0M794t6X0p+HRb5SKGPPa/v4q3Pg21TRVcKq3EUpyRaKjF
	XFScCAAdX0OLYQIAAA==
X-Seq: zsh-workers 38133

On Fri, 11 Mar 2016 14:47:29 +0100
Vincent Lefevre <vincent@vinc17.net> wrote:
> With zsh 5.2 under Debian/unstable, zsh sometimes crashes when
> I do:
> 
> cventin:~/software/mutt/mutt> ./configure --[TAB]

> #0  0x000000000046f315 in charrefinc (x=0x6c58b8 <patinput>, y=0x7fd0f708c3c4 <error: Cannot access memory at address 0x7fd0f708c3c4>, z=0x7ffd49191418) at ../../Src/pattern.c:1937
>         wc = 0 L'\000'
>         ret = <optimized out>

Looks like something's already gone wrong by this point, since

> #1  0x0000000000472a0a in patmatch (prog=prog@entry=0xa00948) at ../../Src/pattern.c:2718
>         savpatinput = 0x7fd0f708c3b8 <error: Cannot access memory at address 0x7fd0f708c3b8>

this has remembered the value of an apparently invalid previous value of
patinput up above... although that's not guaranteed, since it may
simply be pointing to tne end of memory, which is valid as long as it's
not dereferenced (I had this while debugging a few months ago).

Does valgrind give any information?

pws