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/55059] New: DWARF missing concrete class definition
Date: Wed, 24 Oct 2012 15:52:00 -0000	[thread overview]
Message-ID: <bug-55059-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55059
           Summary: DWARF missing concrete class definition
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: tromey@gcc.gnu.org


Created attachment 28519
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28519
test program

This comes from http://sourceware.org/bugzilla/show_bug.cgi?id=14760

I think GCC master from today generates invalid, or at least
questionable, DWARF for the attached test case.
This causes gdb test suite failures.

The bug is in the DWARF for the instantiation of Base.
Current GCC emits:

 <1><f1>: Abbrev Number: 15 (DW_TAG_structure_type)
    <f2>   DW_AT_name        : (indirect string, offset: 0x191): Base<long int,
47, (& a_global), &S::f>    
    <f6>   DW_AT_byte_size   : 1    
    <f7>   DW_AT_decl_file   : 1    
    <f8>   DW_AT_decl_line   : 30    
    <f9>   DW_AT_declaration : 1    
    <f9>   DW_AT_sibling     : <0x155>    

This has DW_AT_declaration -- but there is no concrete instance of the type.

Previous versions of GCC omitted this attribute.  For example, Fedora 16
GCC:

 <1><f1>: Abbrev Number: 10 (DW_TAG_structure_type)
    <f2>   DW_AT_name        : (indirect string, offset: 0x135): Base<long int,
47, (& a_global), &S::f>    
    <f6>   DW_AT_byte_size   : 1    
    <f7>   DW_AT_decl_file   : 1    
    <f8>   DW_AT_decl_line   : 30    
    <f9>   DW_AT_sibling     : <0x155>    

I think the previous approach is preferable.


             reply	other threads:[~2012-10-24 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 15:52 tromey at gcc dot gnu.org [this message]
2012-10-25  7:00 ` [Bug debug/55059] " jakub at gcc dot gnu.org
2012-12-09  2:34 ` [Bug debug/55059] [4.8 Regression] " pinskia at gcc dot gnu.org
2012-12-17 14:48 ` jakub at gcc dot gnu.org
2013-01-03 19:29 ` tromey at gcc dot gnu.org
2013-01-28  1:54 ` jason at gcc dot gnu.org
2013-01-28 20:08 ` tromey at gcc dot gnu.org
2013-01-31 17:48 ` jason at gcc dot gnu.org
2013-01-31 18:29 ` jason at gcc dot gnu.org
2013-01-31 18:32 ` jason 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-55059-4@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).