public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Peter Thompson <peter.thompson@etnus.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: debug/10156: g++ 3.2 fails to emit debug location info for a local variable inside a class constructor
Date: Wed, 19 Mar 2003 22:46:00 -0000	[thread overview]
Message-ID: <20030319224600.20285.qmail@sources.redhat.com> (raw)

The following reply was made to PR debug/10156; it has been noted by GNATS.

From: Peter Thompson <peter.thompson@etnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: debug/10156: g++ 3.2 fails to emit debug location info for a
 local variable inside a class constructor
Date: Wed, 19 Mar 2003 17:42:46 -0500

 Thanks Daniel,
 
 I looked at 1141, and concur with your analysis, since it agrees with 
 ours ;-)  It was submitted only a week ago, so I'm not too surprised it 
 hasn't been hit yet.
 
 Regards,
 PeterT
 
 
 Daniel Jacobowitz wrote:
 > On Wed, Mar 19, 2003 at 10:22:11PM -0000, peter.thompson@etnus.com wrote:
 > 
 >>>Number:         10156
 >>>Category:       debug
 >>>Synopsis:       g++ 3.2 fails to emit debug location info for a local variable inside a class constructor
 >>>Confidential:   no
 >>>Severity:       critical
 >>>Priority:       medium
 >>>Responsible:    unassigned
 >>>State:          open
 >>>Class:          sw-bug
 >>>Submitter-Id:   net
 >>>Arrival-Date:   Wed Mar 19 22:26:00 UTC 2003
 >>>Closed-Date:
 >>>Last-Modified:
 >>>Originator:     Peter Thompson - Etnus
 >>>Release:        gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
 >>>Organization:
 >>>Environment:
 >>
 >>i686 platform
 >>gcc 3.2 compilers (also tried 3.2.1, and 3.2.2 versions with same results)
 >>
 >>>Description:
 >>
 >>We ran into this problem with our debugger, TotalView, but were able to replicate the problem, with a little bit of effort, with gdb.
 > 
 > 
 > Just FYI, the same problem was reported as a GDB bug c++/1141; I
 > forwarded it to gcc-bugs and got no response, and haven't had time to
 > look at it myself.  There's a smaller testcase there.
 > 
 


             reply	other threads:[~2003-03-19 22:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19 22:46 Peter Thompson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-19 22:36 Daniel Jacobowitz
2003-03-19 22:26 peter.thompson

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=20030319224600.20285.qmail@sources.redhat.com \
    --to=peter.thompson@etnus.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).