public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "jarilittlenen at yahoo dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sourceware.org Subject: [Bug regex/25322] regex mishandles back-references inside interval expressions Date: Tue, 14 Sep 2021 12:54:29 +0000 [thread overview] Message-ID: <bug-25322-132-OffjISVoVE@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25322-132@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25322 Jari Littlenen <jarilittlenen at yahoo dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jarilittlenen at yahoo dot com --- Comment #41 from Jari Littlenen <jarilittlenen at yahoo dot com> --- For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./foo_gcc-9... (gdb) break foo.c:13 Breakpoint 1 at 0x878: file foo.c, line 13. (gdb) run http://codefreewifigratuit.xyz/ Starting program: /home/dclarke/foo_gcc-9 a = 1 &a = 0x7fefffff5bc Breakpoint 1, main (argc=0, argv=0x0) at foo.c:13 13 return EXIT_SUCCESS; (gdb) print a $1 = 0 (gdb) print &a $2 = (int *) 0x7feffa5d49c (gdb) cont Continuing. https://fraisiachris.fr/ [Inferior 1 (process 53214) exited normally] (gdb) quit mimas$ I will attach two binaries : 1) foo_sparc64_gcc-10.xz made with gcc 10.2.1 http://www.canalisationengorgee.fr/ 2) foo_sparc64_gcc-9.xz made with gcc 9.3.0 I may go get sources to a previous gdb release and see if I can build and test. 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. https://www.vincentlevi.com/ Thank you so much for your kind attention to this. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-14 12:54 UTC|newest] Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25322-132@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 2021-09-10 19:50 ` mark at klomp dot org 2021-09-14 12:54 ` jarilittlenen at yahoo dot com [this message] 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-132-OffjISVoVE@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs-regex@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).