public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Alexander.Richardson at cl dot cam.ac.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/99814] regexec fails with -fsanitize=address Date: Tue, 30 Mar 2021 12:06:30 +0000 [thread overview] Message-ID: <bug-99814-4-05ASwqnxW4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99814-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99814 Alex Richardson <Alexander.Richardson at cl dot cam.ac.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Alexander.Richardson at cl dot cam | |.ac.uk --- Comment #5 from Alex Richardson <Alexander.Richardson at cl dot cam.ac.uk> --- Does the sanitizer runtime library include the https://reviews.llvm.org/D96348 patch? IMO the real issue is that dlsym() with RTLD_NEXT selects the oldest versioned symbol. Not sure why that behaviour was chosen. I'm sure there are lots of other sanitizer interceptors that are also affected by https://sourceware.org/bugzilla/show_bug.cgi?id=1319.
next prev parent reply other threads:[~2021-03-30 12:06 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-29 9:44 [Bug sanitizer/99814] New: " stefansf at linux dot ibm.com 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 [this message] 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-05ASwqnxW4@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).