public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at physics dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/10156] [3.3/3.4 Regression] g++ 3.2 fails to emit debug location info for a local variable inside a class constructor
Date: Sat, 05 Jul 2003 16:35:00 -0000	[thread overview]
Message-ID: <20030705163531.21591.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030319222600.10156.peter.thompson@etnus.com>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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


pinskia at physics dot uc dot edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2003-06-02 01:30:36         |2003-07-05 16:35:31
               date|                            |
            Summary|g++ 3.2 fails to emit debug |[3.3/3.4 Regression] g++ 3.2
                   |location info for a local   |fails to emit debug location
                   |variable inside a class     |info for a local variable
                   |constructor                 |inside a class constructor
   Target Milestone|---                         |3.3.1


------- Additional Comments From pinskia at physics dot uc dot edu  2003-07-05 16:35 -------
Most likely the same bug as bug 11098 which is for destructors.
Also in 2.95.3, I can print out the variable i (compiled with -gdwarf-2) so this is a 
regression.


  parent reply	other threads:[~2003-07-05 16:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030319222600.10156.peter.thompson@etnus.com>
2003-06-02  1:26 ` [Bug debug/10156] " peter.thompson@etnus.com
2003-06-02  1:30 ` pinskia@physics.uc.edu
2003-06-02 15:49 ` drow@mvista.com
2003-07-05 16:35 ` pinskia at physics dot uc dot edu [this message]
2003-07-15  1:12 ` [Bug debug/10156] [3.3/3.4 Regression] " mmitchel 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=20030705163531.21591.qmail@sources.redhat.com \
    --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).