This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: question about regex

From: Paul Eggert <eggert at cs dot ucla dot edu>
To: liqingqing <liqingqing3 at huawei dot com>, Tim Rühsen <tim dot ruehsen at gmx dot de>
Cc: libc-alpha at sourceware dot org, Florian Weimer <fweimer at redhat dot com>, Carlos O'Donell <carlos at redhat dot com>, Hushiyuan <hushiyuan at huawei dot com>, Liusirui <liusirui at huawei dot com>
Date: Tue, 21 Jan 2020 00:57:18 -0800
Subject: Re: question about regex
References: <fe3eef9c-740e-9b83-c472-59f8e2353b86@huawei.com> <e92f791d-7448-17ce-2820-a968770791b6@huawei.com> <fe84ed3d-6bbc-ea87-4e50-93e11736b005@gmx.de> <05dfac46-6cf3-1f5d-14e7-3c8b07b2093e@cs.ucla.edu> <377311fb-fdf3-6467-3b48-28404d8c3326@huawei.com> <dbd2cdae-5a33-593e-83d8-6a3fd0f85afb@huawei.com> <034194cc-908b-d29f-5ee7-9cf273868ff0@cs.ucla.edu> <10479390-8a29-07f3-2d80-ebc7c340fe64@huawei.com>

On 1/20/20 5:15 PM, liqingqing wrote:

The proposal is that I want to find a way to fix the bug#24269(infinite loop bugs).

Why is this urgent? Even if you fix this particular bug correctly (instead ofmerely putting in an arbitrary backtrack limit), there are lots of ways to makethe regex code explode exponentially and I don't see the practical differencebetween doing that and looping forever.

References:
- question about regex
  - From: liqingqing
- Re: question about regex
  - From: Tim Rühsen
- Re: question about regex
  - From: Paul Eggert
- Re: question about regex
  - From: liqingqing
- Re: question about regex
  - From: liqingqing
- Re: question about regex
  - From: Paul Eggert
- Re: question about regex
  - From: liqingqing

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]