public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/60142] [4.9 Regression][asan] -fsanitize=address breaks debugging - stepping into functions no longer possible
Date: Wed, 12 Feb 2014 14:35:00 -0000 [thread overview]
Message-ID: <bug-60142-4-eVHBHkWx8S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60142-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60142
Jan Kratochvil <jan.kratochvil at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jan.kratochvil at redhat dot com
--- Comment #4 from Jan Kratochvil <jan.kratochvil at redhat dot com> ---
Verified GDB fails with it.
GDB puts breakpoint on second ".loc" (that is not the fist/initial ".loc") in a
function as currently neither GCC nor GCC use DW_LNS_set_prologue_end.
g++ (GCC) 4.9.0 20140212 (experimental)
-S -g -fsanitize=address
.type _Z4testv, @function
_Z4testv:
.LASANPC512:
.LFB512:
.file 2 "asantest.C"
.loc 2 4 0
.cfi_startproc
.cfi_personality 0x3,__gxx_personality_v0
.cfi_lsda 0x3,.LLSDA512
pushq %rbp
.cfi_def_cfa_offset 16
.cfi_offset 6, -16
movq %rsp, %rbp
.cfi_def_cfa_register 6
pushq %r14
pushq %r13
pushq %r12
pushq %rbx
subq $112, %rsp
.cfi_offset 14, -24
.cfi_offset 13, -32
.cfi_offset 12, -40
.cfi_offset 3, -48
leaq -128(%rbp), %rbx
movq %rbx, %r14
cmpl $0, __asan_option_detect_stack_use_after_return(%rip)
je .L3
.loc 2 4 0
<--- here GDB puts the breakpoint
movq %rbx, %rsi
movl $96, %edi
call __asan_stack_malloc_1
movq %rax, %rbx
.L3:
GDB already workarounds a similar case of GCC PR debug/48827, this asan
prologue may look standard enough it could be possibly also workarounded in
GDB.
next prev parent reply other threads:[~2014-02-12 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 11:14 [Bug sanitizer/60142] New: " burnus at gcc dot gnu.org
2014-02-11 13:36 ` [Bug sanitizer/60142] " rguenth at gcc dot gnu.org
2014-02-11 14:20 ` jakub at gcc dot gnu.org
2014-02-11 15:05 ` burnus at gcc dot gnu.org
2014-02-12 14:35 ` jan.kratochvil at redhat dot com [this message]
2014-02-18 13:00 ` jakub at gcc dot gnu.org
2014-02-18 13:08 ` jan.kratochvil at redhat dot com
2014-02-18 13:59 ` jakub at gcc dot gnu.org
2014-02-18 14:14 ` jan.kratochvil at redhat dot com
2014-02-18 16:52 ` jan.kratochvil at redhat dot com
2014-02-18 21:16 ` jakub at gcc dot gnu.org
2014-02-18 21:17 ` 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-60142-4-eVHBHkWx8S@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: link
Be 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).