public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "y.gribov at samsung dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/58718] New: Invalid check in libsanitizer Date: Mon, 14 Oct 2013 06:02:00 -0000 [thread overview] Message-ID: <bug-58718-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58718 Bug ID: 58718 Summary: Invalid check in libsanitizer Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: y.gribov at samsung dot 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 Created attachment 30998 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30998&action=edit Repro I've recently tried to run AddressSanitizer with malloc_context_size=0 runtime option to speedup execution of my program. I got nice perf improvements but also an internal abort in asan_allocator2.cc when it tried to report heap overflow warning: 0x60040000e004 is located 4 bytes to the right of 16-byte region [0x60040000dff0,0x60040000e000) ==3488== AddressSanitizer CHECK failed: /home/ygribov/gcc/gcc-master/libsanitizer/asan/asan_allocator2.cc:216 "((id)) != (0)" (0x0, 0x0) If I unset ASAN_OPTIONS, warning is reported correctly. -Y
next reply other threads:[~2013-10-14 6:02 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-14 6:02 y.gribov at samsung dot com [this message] 2013-10-14 6:03 ` [Bug sanitizer/58718] " y.gribov at samsung dot com 2013-10-14 6:36 ` y.gribov at samsung dot com 2013-10-14 6:49 ` kcc at gcc dot gnu.org 2013-11-05 8:21 ` y.gribov at samsung dot com 2013-11-05 18:58 ` tetra2005 at gmail dot com 2013-12-31 5:34 ` y.gribov at samsung 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-58718-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).