X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 11 Feb 2010 22:29:38 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [gcc] FYI, libffi FAILs with cygwin snapshot 20100205, 20100207 & 20100210... Message-ID: <20100211212938.GT28659@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20100211090138 DOT GH28659 AT calimero DOT vinschen DOT de> <475569 DOT 16919 DOT qm AT web25501 DOT mail DOT ukl DOT yahoo DOT com> <20100211160443 DOT GO28659 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100211160443.GO28659@calimero.vinschen.de> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Feb 11 17:04, Corinna Vinschen wrote: > On Feb 11 15:39, Marco Atzeri wrote: > > --- Gio 11/2/10, Corinna Vinschen ha scritto: > > > On Feb 11 07:40, Christian Joensson > > > wrote: > > > > >> Test Run By chj on Wed Feb 10 11:39:41 2010 > > > > > 115,118c115,118 > > > > > < 7 8. 9 1 9. 3: 8 17. 12 > > > > > < res: 8 17. 12 > > > > > < 7 8. 9 1 9. 3: 8 17. 12 > > > > > < res: 8 17. 12 > > > > > --- > > > > >> 7 8 9 1 9 3: 8 17 12 > > > > >> res: 8 17 12 > > > > >> 7 8 9 1 9 3: 8 17 12 > > > > >> res: 8 17 12 > > > > > > > > > > > > > > > Note the crept in "." (dot) which is symptomatic > > > for the situation... > > > > > if this rings a bell in anyone's ear? > > > > > > > > well, maybe this never shows up on cygwin developers' > > > list.. but > > > > > > > > 20100204 works... 20100205 doesn't... > > > > > > That's the same observation Marco made in > > > http://cygwin.com/ml/cygwin/2010-02/msg00257.html > > > and it points to a problem in the new, multibyte-aware > > > regex imported > > > from FreeBSD. > > > > Autom4te::Channels::msg('obsolete.' > > ^ > > also in my case a extra dot is the likely problem. > > Ok, but when and where did it creep in? What's the original search > pattern, what's the string to search? And at which point did the dot > show up? For a start, I just applied a patch to the new regex functions. I used the test file from Henry Spencer together with the test application from glibc, and the results were hair-raising. I did practically nothing else today but to debug this and to minimize the problems with this regex implementation, especially in the multibyte cases. AFAICS there are no really bad problems left. Makes me wonder if this code was really tested at all in FreeBSD :( Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple