public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan dot kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/39372]  New: Missing DW_AT_location for constructor static variable
Date: Thu, 05 Mar 2009 00:12:00 -0000	[thread overview]
Message-ID: <bug-39372-12292@http.gcc.gnu.org/bugzilla/> (raw)

Regression against g++-4.3 for g++-4.4 on the variable `problem':

g++ (GCC) 4.4.0 20090303 (experimental):
 <1><54>: Abbrev Number: 8 (DW_TAG_subprogram)
    <55>   DW_AT_specification: <0x33>  
    <5a>   DW_AT_inline      : 0        (not inlined)
 <2><72>: Abbrev Number: 11 (DW_TAG_lexical_block)
 <3><73>: Abbrev Number: 12 (DW_TAG_variable)
    <74>   DW_AT_name        : (indirect string, offset: 0x14): problem
    <7a>   DW_AT_type        : <0x85>
(DW_AT_location is not found by any abstract_origin or specificatione etc.)

g++ (GCC) 4.4.0 20090219 (Red Hat 4.4.0-0.21):
 <1><54>: Abbrev Number: 8 (DW_TAG_subprogram)
    <55>   DW_AT_specification: <0x33>
    <5a>   DW_AT_inline      : 0        (not inlined)
 <2><73>: Abbrev Number: 12 (DW_TAG_variable)
    <74>   DW_AT_name        : (indirect string, offset: 0x1a): problem
    <7a>   DW_AT_type        : <0x10b>

it worked before - g++ (GCC) 4.3.2 20081105 (Red Hat 4.3.2-7):
 <1><85>: Abbrev Number: 10 (DW_TAG_subprogram)
    <86>   DW_AT_specification: <0x33>
    <8b>   DW_AT_inline      : 0        (not inlined)
 <2><a3>: Abbrev Number: 13 (DW_TAG_variable)
    <a4>   DW_AT_name        : (indirect string, offset: 0x14): problem
    <aa>   DW_AT_type        : <0x7f>
    <ae>   DW_AT_location    : 9 byte block: 3 8 0 0 0 0 0 0 0  (DW_OP_addr: 8)

-------------------------------------------------------------------------------
extern void f (int *);

class A
{
public:
  A(int i);
};

A::A(int i)
{
  static int *problem = new int(i);
  f (problem);                          
}

void f (int *)
{
}

int
main (void)
{
  A a(42);
  return 0;
}


-- 
           Summary: Missing DW_AT_location for constructor static variable
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jan dot kratochvil at redhat dot com
GCC target triplet: x86_64-unknown-linux-gnu


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


             reply	other threads:[~2009-03-05  0:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05  0:12 jan dot kratochvil at redhat dot com [this message]
2009-03-05 10:39 ` [Bug debug/39372] " rguenth at gcc dot gnu dot org
2009-03-05 10:54 ` [Bug debug/39372] [4.3/4.4 Regression] " jakub at gcc dot gnu dot org
2009-03-05 11:14 ` jakub at gcc dot gnu dot org
2009-03-05 15:02 ` jakub at gcc dot gnu dot org
2009-03-06  9:46 ` jakub at gcc dot gnu dot org
2009-03-06 22:50 ` jakub at gcc dot gnu dot org
2009-03-06 22:53 ` [Bug debug/39372] [4.3 " jakub at gcc dot gnu dot org
2009-04-21 15:56 ` jakub at gcc dot gnu dot org
2009-07-22 10:33 ` jakub at gcc dot gnu dot org
2009-10-15 12:53 ` jakub at gcc dot gnu dot org
2010-01-21 13:16 ` jakub at gcc dot gnu dot org
2010-04-30  8:53 ` jakub 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-39372-12292@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).