X-Spam-Check-By: sourceware.org
To: cygwin@cygwin.com
From: Eric Blake <ebb9@byu.net>
Subject:  Re: 1.5.21: segfault with findutils 4.3.1
Date: Wed, 15 Nov 2006 18:45:39 +0000 (UTC)
Lines: 25
Message-ID:  <loom.20061115T194139-750@post.gmane.org>
References:  <455B493A.10405@elektrobit.com> <20061115173258.GB21115@trixie.casa.cgf.cx>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Christopher Faylor <cgf-no-personal-reply-please <at> cygwin.com> writes:

> 
> On Wed, Nov 15, 2006 at 06:07:06PM +0100, Ingmar Sittl wrote:
> >running "find -type f -regex '.*[.]trc'" within any (even an empty) directory
> >leads to the following segfault message:
> >
> >Exception: STATUS_ACCESS_VIOLATION at eip=610DDBC0
> 
> FWIW, that IP seems to be in stpbrk.

This is an upstream bug, due to findutils using an out-of-date regex library 
from gnulib.  The gnulib regex library has fixed the bug in the meantime.  I've 
reported this upstream.  I'll see about getting a new findutils release soon, 
whether that means seeing if upstream will release 4.3.2 in the near future, or 
whether it means trying to patch the 4.3.1 tarball to use a newer snapshot of 
gnulib.

But for your particular example, what's wrong with using the identical behavior 
of "-name '*.trc*'" instead of the faulting "-regex '.*[.]trc'"?

-- 
Eric Blake
volunteer cygwin findutils maintainer



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/