From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28612 invoked by alias); 27 Jan 2004 06:07:36 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 28573 invoked from network); 27 Jan 2004 06:07:34 -0000 Received: from unknown (HELO granger.mail.mindspring.net) (207.69.200.148) by sources.redhat.com with SMTP; 27 Jan 2004 06:07:34 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by granger.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1AlMNk-00034v-00; Tue, 27 Jan 2004 01:07:28 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id DF38A4B363; Tue, 27 Jan 2004 01:07:27 -0500 (EST) To: eliz@gnu.org, gdb-patches@sources.redhat.com Subject: [rfa/doco] PROBLEMS: add gdb/1516 Message-Id: <20040127060727.DF38A4B363@berman.michael-chastain.com> Date: Tue, 27 Jan 2004 06:07:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-01/txt/msg00683.txt.bz2 This patch adds a description of gdb/1516 to the PROBLEMS file. This is a regression with g++ 2.95.3 -gdwarf-2 and we've decided not to fix it, so I want to document it. By the way, this file needs (1) a copyright notice and (2) to be updated from "gdb 6.0" to "gdb 6.1". Leaving those issues aside -- okay to commit this? Michael C 2004-01-27 Michael Chastain * PROBLEMS: add gdb/1516. Index: PROBLEMS =================================================================== RCS file: /cvs/src/src/gdb/PROBLEMS,v retrieving revision 1.20 diff -c -3 -p -r1.20 PROBLEMS *** PROBLEMS 24 Oct 2003 17:37:03 -0000 1.20 --- PROBLEMS 27 Jan 2004 06:04:45 -0000 *************** Fortunately the ARM target, in the GDB's *** 23,28 **** --- 23,40 ---- updated so people encountering problems should consider downloading a more current GDB (http://www.gnu.org/software/gdb/current). + gdb/1516: [regression] local classes, gcc 2.95.3, dwarf-2 + + With gcc 2.95.3 and the dwarf-2 debugging format, classes which are + defined locally to a function include the demangled name of the function + as part of their name. For example, if a function "foobar" contains a + local class definition "Local", gdb will say that the name of the class + type is "foobar__Fi.0:Local". + + This applies only to classes where the class type is defined inside a + function, not to variables defined with types that are defined somewhere + outside any function (which most types are). + gdb/1091: Constructor breakpoints ignored gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints