This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: regexec calls with REG_STARTEND find ghost matches for \>
- From: Florian Weimer <fweimer at redhat dot com>
- To: Benno Schulenberg <bensberg at justemail dot net>
- Cc: libc-alpha at sourceware dot org
- Date: Sun, 25 Jun 2017 18:30:32 +0200
- Subject: Re: regexec calls with REG_STARTEND find ghost matches for \>
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=fweimer at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 71B4B5D687
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 71B4B5D687
- References: <1484508543.319322.848453144.6EF987A1@webmail.messagingengine.com>
On 01/15/2017 08:29 PM, Benno Schulenberg wrote:
> When calling regexec with the REG_STARTEND flag and providing
> an end-of-range value in .rm_eo that points to somewhere in
> the middle of a word, regexec will nevertheless find a match
> for \> at that offset. The corresponding case for \<, with a
> start-of-range value in .rm_so that points to the middle of a
> word, will /not/ find a match for \< there. The latter is
> what I expected, the former was a surprise.
I agree that this looks like a bug. Would you please file it in
Bugzilla? Thanks.
https://sourceware.org/bugzilla/
Florian