From: Paul Eggert <eggert@cs.ucla.edu>
To: liqingqing <liqingqing3@huawei.com>, "Tim Rühsen" <tim.ruehsen@gmx.de>
Cc: libc-alpha@sourceware.org, Florian Weimer <fweimer@redhat.com>,
Carlos O'Donell <carlos@redhat.com>,
Hushiyuan <hushiyuan@huawei.com>, Liusirui <liusirui@huawei.com>
Subject: Re: question about regex
Date: Tue, 21 Jan 2020 00:57:18 -0800 [thread overview]
Message-ID: <a985213c-0e71-d56c-6a7d-f722b873885b@cs.ucla.edu> (raw)
In-Reply-To: <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 of
merely putting in an arbitrary backtrack limit), there are lots of ways to make
the regex code explode exponentially and I don't see the practical difference
between doing that and looping forever.
prev parent reply other threads:[~2020-01-21 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 8:44 [discuss] iconv: what's the purpose of the mtrace in the tst-iconv2.c liqingqing
2020-01-02 10:54 ` question about regex liqingqing
2020-01-02 16:16 ` Tim Rühsen
2020-01-02 22:14 ` Paul Eggert
2020-01-03 8:09 ` liqingqing
2020-01-20 10:41 ` liqingqing
2020-01-20 19:25 ` Paul Eggert
2020-01-21 1:15 ` liqingqing
2020-01-21 8:57 ` Paul Eggert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a985213c-0e71-d56c-6a7d-f722b873885b@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=hushiyuan@huawei.com \
--cc=libc-alpha@sourceware.org \
--cc=liqingqing3@huawei.com \
--cc=liusirui@huawei.com \
--cc=tim.ruehsen@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).