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] regexec fails with -fsanitize=address Date: Tue, 30 Mar 2021 08:39:37 +0000 [thread overview] Message-ID: <bug-99814-4-xatSvnmb6G@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 --- Comment #2 from Stefan Schulze Frielinghaus <stefansf at linux dot ibm.com> --- Breakpoint 4, __interception::InterceptFunction (name=0x3fffd61e8f2 "regexec", ver=0x3fffd61eb7e "GLIBC_2.3.4", ptr_to_real=0x3fffd677d08 <__interception::real_regexec>, func=16779728, wrapper=4398001883504) at /devel/gcc-4/src/libsanitizer/interception/interception_linux.cpp:74 74 void *addr = GetFuncAddr(name, ver); At the end of InterceptFunction we have: (gdb) print addr $1 = (void *) 0x3fffd2e9110 <__GI___regexec> The address itself also LGTM, i.e., `readelf -s /lib64/libc.so.6 | grep regexec` results in: 279: 00000000000e9110 344 FUNC GLOBAL DEFAULT 13 regexec@@GLIBC_2.3.4 ... 25156: 00000000000e9110 344 FUNC LOCAL DEFAULT 13 __GI___regexec However, variables func and wrapper differ (gdb) print func $2 = 16779728 (gdb) print wrapper $3 = 4398001883504 so we return false.
next prev parent reply other threads:[~2021-03-30 8:39 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 [this message] 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-xatSvnmb6G@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).