From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 7695 invoked from network); 22 Jul 2022 11:10:36 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 22 Jul 2022 11:10:36 -0000 Received: (qmail 1398 invoked by uid 550); 22 Jul 2022 11:10:33 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 23810 invoked from network); 22 Jul 2022 02:02:53 -0000 Date: Fri, 22 Jul 2022 14:02:38 +1200 From: Mike Beattie To: musl@lists.openwall.com Message-ID: <20220722020238.GC9838@prometheus.ethernal.org> References: <20220721060819.GB9838@prometheus.ethernal.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20220721060819.GB9838@prometheus.ethernal.org> User-Agent: Mutt/1.10.1 (2018-07-13) Subject: [musl] Re: Bug: BOL/EOL anchors in regex capture groups won't match EOL On Thu, Jul 21, 2022 at 06:08:19PM +1200, Mike Beattie wrote: > Removal of "^|" from the beginning of the trailing capture group: > > $ ./r "(^|[,{}() ]|$)300([,{}() ]|$)" "0000 1111 2222" > regex: (^|[,{}() ]|$)300([,{}() ]|$) > regexec on [100 200 300]: Found Please excuse the usage of "0000 1111 2222", that should be "100 200 300", I was testing some much longer complex paths and regexes, but was distilling the content of this report down to be as concise as possible. I'm also not subscribed, please CC me on replies. Mike. -- Mike Beattie