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 debug/58123] [4.8/4.9/5 Regression] debug line not tracked for last autovariable dtor
Date: Wed, 18 Feb 2015 21:41:00 -0000	[thread overview]
Message-ID: <bug-58123-4-xsrhtrvPYN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58123-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58123

--- Comment #8 from Jan Kratochvil <jan.kratochvil at redhat dot com> ---
(In reply to Aldy Hernandez from comment #7)
> Putting this aside for a second, my question is, do we really want a
> debugging experience where we jump from back from the end of scope, back to
> the declaration of the class?

I do not think so.

Or if so then the destructor call needs to be marked with is_stmt=false; but
GDB currently ignores is_stmt.  It would then show the declaration line during
backtrace from crashed destructor (I am not sure it would be better than the
4.7 last statement of the block).


  parent reply	other threads:[~2015-02-18 21:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-11 11:16 [Bug debug/58123] New: [4.8 " jan.kratochvil at redhat dot com
2013-08-16 13:49 ` [Bug debug/58123] [4.8/4.9 " jakub at gcc dot gnu.org
2013-10-16  9:50 ` jakub at gcc dot gnu.org
2013-10-28 13:18 ` asmwarrior at gmail dot com
2013-11-21 14:24 ` rguenth at gcc dot gnu.org
2014-05-22  9:07 ` [Bug debug/58123] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:28 ` [Bug debug/58123] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-02-18 17:57 ` aldyh at gcc dot gnu.org
2015-02-18 21:13 ` aldyh at gcc dot gnu.org
2015-02-18 21:41 ` jan.kratochvil at redhat dot com [this message]
2015-02-19 17:35 ` aldyh at gcc dot gnu.org
2015-02-20  5:00 ` asmwarrior at gmail dot com
2015-02-21  1:01 ` aldyh at gcc dot gnu.org
2015-02-21  2:57 ` aldyh at gcc dot gnu.org
2021-04-14  0:20 ` cvs-commit 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-58123-4-xsrhtrvPYN@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).