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/65749] sanitizer stack trace pc off by 1 Date: Thu, 16 Apr 2015 12:53:00 -0000 [thread overview] Message-ID: <bug-65749-4-F6YyB6XsKq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65749-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65749 Yury Gribov <y.gribov at samsung dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |y.gribov at samsung dot com --- Comment #2 from Yury Gribov <y.gribov at samsung dot com> --- This is not a bug but rather a design choice - it is hard to compute exact size of preceding instruction on CISC platforms. ASan just decrements 1 because this is enough for tools like addr2line or gdb to symbolize addresses. Replacing by trace[i] would indeed cause invalid symbolization as you already noticed.
next prev parent reply other threads:[~2015-04-16 12:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-12 23:36 [Bug sanitizer/65749] New: " msebor at gcc dot gnu.org 2015-04-13 19:07 ` [Bug sanitizer/65749] " msebor at gcc dot gnu.org 2015-04-16 12:53 ` y.gribov at samsung dot com [this message] 2015-04-16 12:53 ` y.gribov at samsung dot com 2015-04-16 13:00 ` 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-65749-4-F6YyB6XsKq@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).