From: liqingqing <liqingqing3@huawei.com>
To: <libc-alpha@sourceware.org>, Florian Weimer <fweimer@redhat.com>,
"Carlos O'Donell" <carlos@redhat.com>
Cc: Hushiyuan <hushiyuan@huawei.com>, Liusirui <liusirui@huawei.com>
Subject: question about regex
Date: Thu, 2 Jan 2020 18:54:50 +0800 [thread overview]
Message-ID: <e92f791d-7448-17ce-2820-a968770791b6@huawei.com> (raw)
In-Reply-To: <fe3eef9c-740e-9b83-c472-59f8e2353b86@huawei.com>
Hello Florian and all glibc developers.
I wonder ask you that do we have any plan or good ways to fix up the bug as below:
https://sourceware.org/bugzilla/show_bug.cgi?id=24269
Dhiraj 2019-02-26 06:24:20 UTC
While fuzzing the regex module via hongfuzz
$ echo D | grep -E "$(printf '(\0|)(\\1\\1)*')"
bash: warning: command substitution: ignored null byte in input
Segmentation fault (core dumped)
==6453== Process terminating with default action of signal 13 (SIGPIPE)
==6453== at 0x4F4C154: write (write.c:27)
==6453== by 0x4EC71BC: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1203)
==6453== by 0x4EC8F50: new_do_write (fileops.c:457)
==6453== by 0x4EC8F50: _IO_do_write@@GLIBC_2.2.5 (fileops.c:433)
==6453== by 0x4EC6787: _IO_file_sync@@GLIBC_2.2.5 (fileops.c:813)
==6453== by 0x4EBA87C: fflush (iofflush.c:40)
==6453== by 0x10CE73: ??? (in /bin/echo)
==6453== by 0x10C939: ??? (in /bin/echo)
==6453== by 0x10A221: ??? (in /bin/echo)
==6453== by 0x4E7F040: __run_exit_handlers (exit.c:108)
==6453== by 0x4E7F139: exit (exit.c:139)
==6453== by 0x4E5DB9D: (below main) (libc-start.c:344)
==6453==
OS: Linux ubuntu 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
next prev parent reply other threads:[~2020-01-02 10:55 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 ` liqingqing [this message]
2020-01-02 16:16 ` question about regex 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
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=e92f791d-7448-17ce-2820-a968770791b6@huawei.com \
--to=liqingqing3@huawei.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=hushiyuan@huawei.com \
--cc=libc-alpha@sourceware.org \
--cc=liusirui@huawei.com \
/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).