public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stefansf at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/99814] New: regexec fails with -fsanitize=address Date: Mon, 29 Mar 2021 09:44:02 +0000 [thread overview] Message-ID: <bug-99814-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99814 Bug ID: 99814 Summary: regexec fails with -fsanitize=address Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: stefansf at linux dot ibm.com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- Target: s390x Testing against today's commit https://gcc.gnu.org/g:d579e2e76f9469e1b386d693af57c5c4f0ede410 on s390x we have: $ gcc pr98920.c -fsanitize=address && ./a.out failed to match The testcase succeeds without `-fsanitize=address`. In GDB I see that the address loaded from _ZN14__interception12real_regexecE equals the address of regexec@GLIBC_2.2 which explains why the testcase fails. Without `-fsanitize=address` function regexec@@GLIBC_2.3.4 is executed.
next reply other threads:[~2021-03-29 9:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-29 9:44 stefansf at linux dot ibm.com [this message] 2021-03-30 7:36 ` [Bug sanitizer/99814] " marxin at gcc dot gnu.org 2021-03-30 8:39 ` stefansf at linux dot ibm.com 2021-03-30 8:58 ` marxin at gcc dot gnu.org 2021-03-30 11:33 ` stefansf at linux dot ibm.com 2021-03-30 12:06 ` Alexander.Richardson at cl dot cam.ac.uk 2021-03-30 12:09 ` marxin at gcc dot gnu.org 2021-03-30 12:39 ` jakub at gcc dot gnu.org
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-99814-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).