public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mehmetgelisin at aol dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug regex/25322] regex mishandles back-references inside interval expressions Date: Fri, 10 Sep 2021 19:40:55 +0000 [thread overview] Message-ID: <bug-25322-131-mkuA1Ik5mL@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25322-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25322 Mehmet gelisin <mehmetgelisin at aol dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mehmetgelisin at aol dot com --- Comment #40 from Mehmet gelisin <mehmetgelisin at aol dot com> --- Glibc regular expression code mishandles regular expressions such as: .*((.)\2){2}$ http://www-look-4.com/ as it does not backtrack enough to find a match that satisfies the back-references when they are used twice. To reproduce the problem, compile and run the attached file backrefbug.c. It will exit with status 2, whereas the correct exit status is 0. http://www.compilatori.com/ This bug was originally reported against GNU 'grep' here: http://www.wearelondonmade.com/ and you can find more test cases by reading Now, let's try to debug this: ... $ gdb --args gdb -batch test.c http://www.jopspeech.com/ Reading symbols from /home/vries/gdb_versions/devel/gdb... (gdb) start Temporary breakpoint 1 at 0x417f36: file /home/vries/gdb_versions/devel/src/gdb/gdb.c, line 28. Starting program: /home/vries/gdb_versions/devel/gdb -data-directory /home/vries/gdb_versions/devel/build/gdb/testsuite/../data-directory -q -nw -nx -batch test.c [Thread debugging using libthread_db enabled] http://joerg.li/ Using host libthread_db library "/lib64/libthread_db.so.1". Temporary breakpoint 1, main (argc=8, argv=0x7fffffffdbf8) at /home/vries/gdb_versions/devel/src/gdb/gdb.c:28 28 memset (&args, 0, sizeof args); (gdb) n 29 args.argc = argc; http://connstr.net/ (gdb) n 30 args.argv = argv; (gdb) n 31 args.interpreter_p = INTERP_CONSOLE; (gdb) n 32 return gdb_main (&args); http://embermanchester.uk/ (gdb) n [New Thread 0x7fffefc75700 (LWP 11712)] [New Thread 0x7fffef474700 (LWP 11713)] [New Thread 0x7fffeec73700 (LWP 11714)] [Detaching after vfork from child process 11715] http://www.slipstone.co.uk/ [New Thread 0x7fffee156700 (LWP 11716)] [New Thread 0x7fffe7fff700 (LWP 11717)] [New Thread 0x7fffed955700 (LWP 11718)] http://www.logoarts.co.uk/ [New Thread 0x7fffed154700 (LWP 11719)] /home/vries/gdb_versions/devel/src/gdb/infrun.c:6384: internal-error: void process_event_stop_test(execution_control_state*): http://www.acpirateradio.co.uk/ Assertion `ecs->event_thread->control.exception_resume_breakpoint != NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. https://waytowhatsnext.com/ Quit this debugging session? [New Thread 0x7fffefc75700 (LWP 11712)] [New Thread 0x7fffef474700 (LWP 11713)] [New Thread 0x7fffeec73700 (LWP 11714)] https://www.webb-dev.co.uk/ [Detaching after vfork from child process 11715] [New Thread 0x7fffefc75700 (LWP 11712)] [New Thread 0x7fffef474700 (LWP 11713)] [New Thread 0x7fffeec73700 (LWP 11714)] http://www.iu-bloomington.com/ [Detaching after vfork from child process 11715] [New Thread 0x7fffefc75700 (LWP 11712)] [New Thread 0x7fffef474700 (LWP 11713)] [New Thread 0x7fffeec73700 (LWP 11714)] [Detaching after vfork from child process 11715] -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-10 19:40 UTC|newest] Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25322-131@http.sourceware.org/bugzilla/> 2021-05-25 19:52 ` ahmedsayeed1982 at yahoo dot com 2021-06-15 23:40 ` lmminformation2020 at gmail dot com 2021-06-27 17:41 ` ahmedsayeed1982 at yahoo dot com 2021-07-07 13:08 ` lexenluis at gmail dot com 2021-07-07 13:48 ` lexenluis at gmail dot com 2021-07-08 2:21 ` lexenluis at gmail dot com 2021-07-12 16:33 ` lexenluis at gmail dot com 2021-07-13 0:17 ` ampva300 at gmail dot com 2021-07-15 1:14 ` sherrixotyv29 at gmail dot com 2021-07-16 13:50 ` afarabdelwahab at gmail dot com 2021-07-16 13:51 ` afarabdelwahab at gmail dot com 2021-07-16 13:52 ` afarabdelwahab at gmail dot com 2021-07-16 17:21 ` lexenluis at gmail dot com 2021-07-18 10:32 ` lexenluis at gmail dot com 2021-07-21 3:36 ` sherrixotyv29 at gmail dot com 2021-07-21 7:59 ` lexenluis at gmail dot com 2021-07-24 0:15 ` namboru at jasaseo dot one 2021-07-24 2:36 ` bhtrananh8 at gmail dot com 2021-07-25 8:36 ` lexenluis at gmail dot com 2021-07-26 13:01 ` lexenluis at gmail dot com 2021-07-28 7:24 ` noithatduyanh.1990 at gmail dot com 2021-07-30 4:33 ` lexenluis at gmail dot com 2021-08-03 12:15 ` lexenluis at gmail dot com 2021-08-07 9:55 ` sosanhgiacomcom1 at gmail dot com 2021-08-08 16:01 ` lexenluis at gmail dot com 2021-08-09 9:33 ` phillipsaeverett84 at gmail dot com 2021-08-09 17:13 ` contact at 200iso dot fr 2021-08-10 11:45 ` ucelsanicin at yahoo dot com 2021-08-11 12:10 ` lexenluis at gmail dot com 2021-08-11 14:33 ` freelancertamal3 at gmail dot com 2021-08-12 2:04 ` seocontentmachine11 at gmail dot com 2021-08-12 2:06 ` seocontentmachine11 at gmail dot com 2021-08-19 5:54 ` ucelsanicin at yahoo dot com 2021-08-23 4:59 ` marlenesanchez231+jaime at gmail dot com 2021-08-27 17:55 ` ribevi6798 at enamelme dot com 2021-08-28 18:31 ` buranlevent at yahoo dot com 2021-09-01 3:21 ` support at shirtwell dot store 2021-09-02 9:02 ` yahoups at hotmail dot fr 2021-09-05 7:38 ` kimolsun2020 at yahoo dot com 2021-09-10 19:40 ` mehmetgelisin at aol dot com [this message] 2021-09-10 19:50 ` mark at klomp dot org 2021-09-14 12:54 ` jarilittlenen at yahoo dot com 2021-09-14 17:25 ` johnb6174 at gmail dot com 2021-09-14 17:26 ` johnb6174 at gmail dot com 2021-09-14 17:27 ` johnb6174 at gmail dot com 2021-09-16 8:18 ` gavalo6262 at stvbz dot com 2021-09-18 13:42 ` mediathek at berlin dot com 2021-09-22 16:40 ` mervegunesli at aol dot com 2021-09-25 10:21 ` frankdecender at gmail dot com 2021-09-25 10:29 ` frankdecender at gmail dot com 2021-09-25 10:38 ` frankdecender at gmail dot com 2021-09-25 10:42 ` frankdecender at gmail dot com 2021-09-28 1:22 ` marlenesanchez231+jaime at gmail dot com 2021-09-30 9:18 ` iamcreaturescience09 at gmail dot com 2021-10-01 2:45 ` luongnhattanarsenal13 at gmail dot com 2021-10-02 14:45 ` teampakrush at gmail dot com 2021-10-04 19:45 ` portlandjunkremovalservice at gmail dot com 2021-10-04 22:55 ` gutterinstallationarvada at gmail dot com 2021-10-08 6:59 ` Isobelle_marin at protonmail dot com 2021-10-09 11:00 ` gulsenenginar at aol dot com 2021-10-14 8:49 ` alwafaacampany9 at gmail dot com 2021-10-14 8:51 ` alwafaacampany9 at gmail dot com 2021-10-14 8:56 ` alwafaacampany9 at gmail dot com 2021-10-17 19:48 ` vmireskazki at gmail dot com 2021-10-18 19:57 ` ahmedsayeed1982 at hotmail dot com 2021-10-19 7:15 ` progonsaytu at gmail dot com 2021-10-19 14:17 ` adhemerval.zanella at linaro dot org 2021-10-21 6:55 ` bap.fayol at gmail dot com 2021-10-21 6:56 ` bap.fayol at gmail dot com 2021-10-22 13:43 ` mailme at iaiamedia dot be 2021-10-22 15:09 ` john at architectengroep dot com 2021-10-23 13:45 ` fiteva5725 at bomoads dot com 2021-10-24 10:03 ` glassmtech at ukr dot net 2021-10-24 10:03 ` glassmtech at ukr dot net 2021-10-26 15:52 ` david at hailproco dot com 2021-10-29 7:30 ` paulomail at artestudiogallery dot it 2021-10-29 10:56 ` kimolsun2020 at outlook dot com 2021-11-02 8:00 ` site1 at flyhigh dot co.in 2021-11-06 21:11 ` paneki8601 at dukeoo dot com 2021-11-13 19:30 ` tesaso8237 at funboxcn dot com 2021-11-25 11:28 ` joyruth102798 at gmail dot com 2022-11-02 10:07 ` bhtrananh8 at gmail dot com
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-25322-131-mkuA1Ik5mL@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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: linkBe 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).