GNU bug report logs - #18425
test for new glibc regex bug

Previous Next

Full log

Message #17 received at 18425 <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 18425 <18425 <at> debbugs.gnu.org>
Subject: Re: bug#18425: test for new glibc regex bug
Date: Thu, 11 Sep 2014 08:00:16 -0700

On Wed, Sep 10, 2014 at 8:40 PM, Paul Eggert <eggert <at> cs.ucla.edu> wrote:
> Jim Meyering wrote:
>>
>> what about configure's --without-included-regex option?
>> With it, the test may well pass (counted as a failure, here) on
>> systems without glibc.
>
>
> Grep uses the glibc interface for regular expressions, and I expect that
> every current implementation of that interface has the bug, so this
> shouldn't be an issue now (though it would be an issue if the bug is ever
> fixed).
>
> Or were you thinking of glibc 2.2.6 and earlier?  That might not have the
> bug, as it predates the circa-2002 regex rewrite that introduced the bug.  I
> suspect, though, that 2.2.6 regex would fail several other tests.  Are glibc
> versions this old still being used?
>
> (Do users really complain when XFAIL tests succeed instead of failing as
> predicted?  Dumb question, I know; they'll complain about anything....)

That's it. When an XFAIL test passes, the framework counts
it as a failure and requests that a report including test-suite.log
be sent to the bug-reporting address. I have found that it is
almost always worthwhile to invest in avoiding those :-)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.