public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eggert at gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/59600] New: no_sanitize_address mishandled when function is inlined Date: Thu, 26 Dec 2013 01:57:00 -0000 [thread overview] Message-ID: <bug-59600-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59600 Bug ID: 59600 Summary: no_sanitize_address mishandled when function is inlined Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: eggert at gnu dot org 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 Created attachment 31514 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31514&action=edit Compile and link with '-fsanitize=address -O2' and run to illustrate the bug A function declared with __attribute__ ((no_sanitize_address)) will attempt to sanitize its addresses if the function happens to be inlined in another function that lacks the attribute. This will cause the code to dump core even when it's not supposed to. I discovered this problem when trying to use address sanitization in Emacs. To reproduce the problem on an x86-64 platform, compile the attached program with 'gcc -fsanitize=address -O2'. It will dump core because the commented address is sanitized even though it's in a no_sanitize_address function. Compiling with -DTHIS_WORKS_AROUND_THE_BUG works around the bug by adding a noinline attribute to the function in question, but user code shouldn't have to do that.
next reply other threads:[~2013-12-26 1:57 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-26 1:57 eggert at gnu dot org [this message] 2013-12-26 5:04 ` [Bug sanitizer/59600] " y.gribov at samsung dot com 2013-12-26 6:04 ` kcc at gcc dot gnu.org 2013-12-26 7:17 ` pinskia at gcc dot gnu.org 2013-12-26 7:24 ` pinskia at gcc dot gnu.org 2013-12-26 7:55 ` y.gribov at samsung dot com 2013-12-26 8:16 ` pinskia at gcc dot gnu.org 2013-12-27 5:07 ` y.gribov at samsung dot com 2014-02-05 5:23 ` ygribov at gcc dot gnu.org 2014-02-05 5:26 ` y.gribov at samsung dot com 2014-02-05 5:32 ` eggert at gnu dot 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-59600-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).