public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: miwako.tokugawa@intel.com
To: gcc-gnats@gcc.gnu.org
Subject: debug/8188: DW_AT_containing_type incorrectly emitted
Date: Thu, 10 Oct 2002 10:56:00 -0000	[thread overview]
Message-ID: <20021010175104.25040.qmail@sources.redhat.com> (raw)


>Number:         8188
>Category:       debug
>Synopsis:       DW_AT_containing_type incorrectly emitted
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Oct 10 10:56:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     miwako.tokugawa@intel.com
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
It seems that g++ misuses DW_AT_containing_type. If you compile test.cpp (attached), we see this.
<1><d5e>: Abbrev Number: 15 (DW_TAG_structure_type)
     DW_AT_sibling     : <df0>  
     DW_AT_name        : B      
     DW_AT_byte_size   : 12     
     DW_AT_decl_file   : 1      
     DW_AT_decl_line   : 12     
     DW_AT_containing_type: <cc4>       
Dwarf3 draft (draft7) section 5.12 describes this attribute as being attached DW_TAG_ptr_to_member_type, and it does not describe its use with a structure DIE.

Furthermore, gdb seems to make use of this emission and this is not correct.
>How-To-Repeat:
g++ -gdwarf-2 test.cpp
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/plain; name="test.cpp"
Content-Disposition: inline; filename="test.cpp"

class A {
public:
    int a1;
};
class c {
public:
    int c1;
};
class B : virtual public A {
public:
    int b2;
};
int main()
{
  B pf;
}


             reply	other threads:[~2002-10-10 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 10:56 miwako.tokugawa [this message]
2002-10-10 11:06 Daniel Jacobowitz

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=20021010175104.25040.qmail@sources.redhat.com \
    --to=miwako.tokugawa@intel.com \
    --cc=gcc-gnats@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).