From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-prs-return-14034-listarch-gcc-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 27019 invoked by alias); 19 Jan 2002 16:36:01 -0000
Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-prs/>
List-Post: <mailto:gcc-prs@gcc.gnu.org>
List-Help: <mailto:gcc-prs-help@gcc.gnu.org>
Sender: gcc-prs-owner@gcc.gnu.org
Received: (qmail 27004 invoked by uid 71); 19 Jan 2002 16:36:01 -0000
Date: Sat, 19 Jan 2002 08:36:00 -0000
Message-ID: <20020119163601.27003.qmail@sources.redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
From: Daniel Jacobowitz <drow@mvista.com>
Subject: Re: debug/5433: Severe debugging problems
Reply-To: Daniel Jacobowitz <drow@mvista.com>
X-SW-Source: 2002-01/txt/msg00685.txt.bz2
List-Id: <gcc-prs.sourceware.org>

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

From: Daniel Jacobowitz <drow@mvista.com>
To: Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: debug/5433: Severe debugging problems
Date: Sat, 19 Jan 2002 11:26:42 -0500

 On Sat, Jan 19, 2002 at 05:11:42PM +0100, Peter Schmid wrote:
 > 
 > >Number:         5433
 > >Category:       debug
 > >Synopsis:       Severe debugging problems
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    unassigned
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Sat Jan 19 08:16:00 PST 2002
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Peter Schmid
 > >Release:        3.1 20020117 (experimental)
 > >Organization:
 > TU Darmstadt
 > >Environment:
 > System: Linux kiste 2.4.17 #7 Thu Jan 3 17:21:51 CET 2002 i686 unknown
 > Architecture: i686
 > SuSE 7.3
 > glibc 2.2.4
 > host: i686-pc-linux-gnu
 > build: i686-pc-linux-gnu
 > target: i686-pc-linux-gnu
 > configured with: ../gcc/configure --enable-shared --disable-nls --enable-threads --enable-languages=c,c++,f77,objc
 > >Description:
 > Debugging c++ code on the main line does not work. For example, consider
 > the following code tl.C. The most recent gdb snapshot emits the
 > strange 
 > "Locale = {static none = Internal: global symbol `_ZNSt6locale4noneE' found in ../../../../gcc/libstdc++-v3/src/locale.cc psymtab but not in symtab.
 > _ZNSt6locale4noneE may be an inlined function, or may be a template function
 > (if a template, try specifying an instantiation:
 > _ZNSt6locale4noneE<type>)" 
 > message. 
 > 
 > Printing the variable Locale does not work, either. There is a "Cannot
 > access memory at address 0x0" message, all following methods and
 > variables are not accessible by the debugger, making debugging of c++
 > programs nearly impossible. The most recent gdb 5.1 snapshot does not
 > emit the psymtab/symtab message but the problems encountered are the
 > same.
 > 
 
 These are GDB bugs, not GCC, presumably.  Please file the PR on GDB.
 
 Namespace support in particular is lacking.  I would guess that's what
 you're hitting here.
 
 -- 
 Daniel Jacobowitz                           Carnegie Mellon University
 MontaVista Software                         Debian GNU/Linux Developer