public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/65662] New: AddressSanitizer CHECK failed: ../../../../gcc/libsanitizer/sanitizer_common/sanitizer_allocator.h:835 "((res)) < ((kNumPossibleRegions))" (0x3ffb49, 0x80000) Date: Thu, 02 Apr 2015 12:51:00 -0000 [thread overview] Message-ID: <bug-65662-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65662 Bug ID: 65662 Summary: AddressSanitizer CHECK failed: ../../../../gcc/libsanitizer/sanitizer_common/sanitize r_allocator.h:835 "((res)) < ((kNumPossibleRegions))" (0x3ffb49, 0x80000) Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: schwab@linux-m68k.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, rguenther at suse dot de Target: aarch64-*-* Breakpoint 1, ComputeRegionId (this=0x3ffb737bd60 <__asan::allocator>, mem=4396780879872) at ../../../../gcc/libsanitizer/sanitizer_common/sanitizer_allocator.h:835 835 CHECK_LT(res, kNumPossibleRegions); (gdb) p/x mem $2 = 0x3ffb4900000
next reply other threads:[~2015-04-02 12:51 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-02 12:51 schwab@linux-m68k.org [this message] 2015-04-02 12:51 ` [Bug sanitizer/65662] " schwab@linux-m68k.org 2015-04-02 13:08 ` jakub at gcc dot gnu.org 2015-04-02 13:16 ` rguenth at gcc dot gnu.org 2015-04-02 13:26 ` pinskia at gcc dot gnu.org 2015-04-02 13:31 ` jakub at gcc dot gnu.org 2015-04-02 16:22 ` kcc at gcc dot gnu.org 2015-04-02 16:22 ` kcc at gcc dot gnu.org 2015-04-05 16:11 ` vekumar at gcc dot gnu.org 2015-04-05 20:48 ` jakub at gcc dot gnu.org 2015-04-06 4:44 ` vekumar 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-65662-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).