X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <475569.16919.qm@web25501.mail.ukl.yahoo.com> Date: Thu, 11 Feb 2010 15:39:05 +0000 (GMT) From: Marco Atzeri Subject: Re: [gcc] FYI, libffi FAILs with cygwin snapshot 20100205, 20100207 & 20100210... To: cygwin AT cygwin DOT com In-Reply-To: <20100211090138.GH28659@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes 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 --- Gio 11/2/10, Corinna Vinschen ha scritto: > On Feb 11 07:40, Christian Joensson > wrote: > > > A "diff ../../../objdir-156618/libffi.log > testsuite/libffi.log" (where > > > the first file is the log file when using the > cygwin1.dll snapshot > > > 20100207 and the second file is using the 1.7.1-1 > one) gives me this > > > (as an example): > > > > > > 1c1 > > > < Test Run By chj on Tue Feb =A09 13:17:04 > 2010 > > > --- > > >> 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? > >=20 > > well, maybe this never shows up on cygwin developers' > list.. but > >=20 > > 20100204 works... 20100205 doesn't... >=20 > 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. =20=20 >=20 > The change between 20100204 and 20100205 was a trivial > change to > silence a cheeky gcc, and it only sets locale variables, > which were > undefined before,,, to a start value of 0.=A0 Nothing > else happened, > but still, now we have a misbehaving regex.=A0 How > disappointing. >=20 > The simple fix would be to revert to our old regex > implementation, > but that would mean to give up multibyte-awareness again. >=20 > A bit more complex but more satisfying in the long run is > to find > out what exactly is going wrong. >=20 > What I need is a simple testcase, either a very small piece > of plain C > code which shows the problem with regcomp/regexec, Or, if > you're not > fluent enough in C, it would help to have the input string > and the > search string which misbehave, like this" >=20 > =A0 Input string:=A0 "The quick brown fox jumps over > the lazy dog." > =A0 Search string: "f.x" >=20 > In the meantime I'll have a look to see if I find anything > obvious. >=20 >=20 > Thanks, > Corinna >=20 > --=20 > Corinna Vinschen=A0 =A0 =A0 =A0 =A0 =A0 Marco -- 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