public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/51358] incorrect/missing location for function arg, -O0, without VTA
Date: Mon, 13 Aug 2012 08:56:00 -0000	[thread overview]
Message-ID: <bug-51358-4-TYGdBkTuxW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51358-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51358

--- Comment #7 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-08-13 08:55:05 UTC ---
(In reply to comment #4)
> It would not be helpful, systemtap would then see no data (just not wrong
> data).
> 
> Also at that time location list will need to be used and currently GDB when it
> sees any location list it thinks it no longer needs to skip the prologue.
> OTOH GDB could look at -grecord-gcc-switches first which it currently does not
> so I should just finally implement -grecord-gcc-switches in GDB in such case.

I think seeing wrong data, thus, wrong-debug is never superior over "no debug
info / no data".


  parent reply	other threads:[~2012-08-13  8:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 16:49 [Bug debug/51358] New: missing location mark at gcc dot gnu.org
2011-11-30 21:07 ` [Bug debug/51358] " jan.kratochvil at redhat dot com
2011-12-01 11:08 ` jakub at gcc dot gnu.org
2012-08-06 18:36 ` [Bug debug/51358] incorrect/missing location for function arg, -O0, without VTA rguenth at gcc dot gnu.org
2012-08-12 18:38 ` jan.kratochvil at redhat dot com
2012-08-12 20:22 ` fche at redhat dot com
2012-08-12 20:31 ` mark at gcc dot gnu.org
2012-08-13  8:56 ` rguenth at gcc dot gnu.org [this message]
2012-11-18  4:13 ` [Bug debug/51358] [4.8 Regression] " pinskia at gcc dot gnu.org
2012-11-19  9:10 ` jakub at gcc dot gnu.org
2012-12-06 16:21 ` [Bug debug/51358] " rguenth at gcc dot gnu.org
2013-12-26  0:21 ` fche at redhat dot com

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-51358-4-TYGdBkTuxW@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).