public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/55844] -fsanitize=address -Os -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -m64 doesn't work Date: Wed, 02 Jan 2013 07:13:00 -0000 [thread overview] Message-ID: <bug-55844-4-pcsZE4jDjo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55844-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55844 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2013-01-02 Ever Confirmed|0 |1 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-01-02 07:13:33 UTC --- It has a frame pointer: pushq %rbp .cfi_def_cfa_offset 16 .cfi_offset 6, -16 movq %rsp, %rbp Right there. The issue is you also need to disable shrink wrapping (-fno-shrink-wrap). This again why we should just move over to using the dwarf unwdinder and forget about the manually unwinding the stack.
next prev parent reply other threads:[~2013-01-02 7:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-02 6:26 [Bug sanitizer/55844] New: " hjl.tools at gmail dot com 2013-01-02 7:13 ` pinskia at gcc dot gnu.org [this message] 2013-01-02 7:31 ` [Bug sanitizer/55844] " jakub at gcc dot gnu.org 2013-01-02 17:31 ` kcc at gcc dot gnu.org 2013-01-02 21:07 ` jakub at gcc dot gnu.org 2013-01-03 6:18 ` kcc at gcc dot gnu.org 2013-01-08 8:14 ` jakub at gcc dot gnu.org 2013-01-08 8:45 ` 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-55844-4-pcsZE4jDjo@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).