From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20300 invoked by alias); 19 Mar 2003 22:46:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 20286 invoked by uid 71); 19 Mar 2003 22:46:00 -0000 Date: Wed, 19 Mar 2003 22:46:00 -0000 Message-ID: <20030319224600.20285.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Peter Thompson Subject: Re: debug/10156: g++ 3.2 fails to emit debug location info for a local variable inside a class constructor Reply-To: Peter Thompson X-SW-Source: 2003-03/txt/msg01303.txt.bz2 List-Id: The following reply was made to PR debug/10156; it has been noted by GNATS. From: Peter Thompson To: Daniel Jacobowitz 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. >