public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/37237] Debug information for virtual destructors omits DW_AT_vtable_elem_location
Date: Thu, 14 Nov 2013 16:56:00 -0000	[thread overview]
Message-ID: <bug-37237-4-n92pqaO5FR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-37237-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from Tom Tromey <tromey at gcc dot gnu.org> ---
I was debugging this today:
https://sourceware.org/bugzilla/show_bug.cgi?id=15975

... and ran across this PR again.
GCC is still emitting a virtual destructor with no indication of
its vtable element location:

 <2><37c>: Abbrev Number: 18 (DW_TAG_subprogram)
    <37d>   DW_AT_external    : 1    
    <37d>   DW_AT_name        : ~B    
    <380>   DW_AT_decl_file   : 1    
    <381>   DW_AT_decl_line   : 23    
    <382>   DW_AT_virtuality  : 1    (virtual)
    <383>   DW_AT_containing_type: <0x33d>    
    <387>   DW_AT_declaration : 1    
    <387>   DW_AT_object_pointer: <0x38b>


  parent reply	other threads:[~2013-11-14 16:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-37237-4@http.gcc.gnu.org/bugzilla/>
2011-05-24 13:51 ` tromey at gcc dot gnu.org
2012-07-12 18:34 ` tromey at gcc dot gnu.org
2012-07-13 17:15 ` tromey at gcc dot gnu.org
2013-01-31 19:32 ` jason at gcc dot gnu.org
2013-02-18 15:21 ` tromey at gcc dot gnu.org
2013-02-26  4:35 ` jason at gcc dot gnu.org
2013-11-14 16:56 ` tromey at gcc dot gnu.org [this message]
2008-08-25 19:54 [Bug debug/37237] New: " drow at gcc dot gnu dot org
2010-02-11 18:44 ` [Bug debug/37237] " dodji at gcc dot gnu dot org
2010-02-12 15:48 ` dodji at gcc dot gnu dot org
2010-02-12 15:52 ` drow at gcc dot gnu dot org
2010-02-21 16:47 ` dodji at gcc dot gnu dot org
2010-02-23 16:56 ` tromey at gcc dot gnu dot org
2010-02-26 12:59 ` dodji at gcc dot gnu dot org
2010-02-26 20:48 ` jason at gcc dot gnu dot 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-37237-4-n92pqaO5FR@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).