public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <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: Tue, 18 Feb 2014 13:00:00 -0000	[thread overview]
Message-ID: <bug-60142-4-yCiVEarhAM@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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
BTW, the second line change in the function heuristics also fails for say:
#include <stdarg.h>

void bar (va_list ap);

void
foo (int a, ...)
{
  va_list ap;
  va_start (ap, a);
  bar (ap);
  va_end (ap);
}

on x86_64, even in that case we emit the second line change on the start of the
second basic block, rather than treating all the prologue and prologue-like
basic blocks as no change in the locus (well, if they are out of line, as in
the case of the varargs x86_64 function that might need saving xmm registers,
or in the -fsanitize=address case, the code conditionally jumps out of line and
then branches back, supposedly we need line directive on the out of line part
of the code).  So, does GDB have a disassemble matcher for the ... prologue, or
does that fail too?


  parent reply	other threads:[~2014-02-18 13:00 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
2014-02-18 13:00 ` jakub at gcc dot gnu.org [this message]
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-yCiVEarhAM@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).