From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26987 invoked by alias); 16 Jan 2009 17:19:29 -0000 Received: (qmail 26979 invoked by uid 22791); 16 Jan 2009 17:19:29 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 16 Jan 2009 17:18:47 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 0D49410630; Fri, 16 Jan 2009 17:18:45 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id E9351105BD; Fri, 16 Jan 2009 17:18:44 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1LNsLD-0006z3-Uf; Fri, 16 Jan 2009 12:18:43 -0500 Date: Fri, 16 Jan 2009 17:19:00 -0000 From: Daniel Jacobowitz To: Christophe LYON Cc: gdb@sourceware.org Subject: Re: gdb.cp/templates.exp, ctor/dtor breakpoints, etc.... Message-ID: <20090116171843.GA26829@caradoc.them.org> Mail-Followup-To: Christophe LYON , gdb@sourceware.org References: <49705F42.5080609@st.com> <20090116150357.GA14717@caradoc.them.org> <4970BFAC.2070301@st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4970BFAC.2070301@st.com> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-01/txt/msg00098.txt.bz2 On Fri, Jan 16, 2009 at 06:11:08PM +0100, Christophe LYON wrote: > Doing this, I follow GCC behaviour, but I get a regression. If we don't > consider this a GCC bug, it means that the way GDB recognizes ctor/dtor > (any probably any overloaded function) is to be revisited? Am I right? Yes, all of the name recognition stuff is broken. We shouldn't be relying on mangled names, since there are compilers we can not change as easily as GCC or yours that do not emit them. -- Daniel Jacobowitz CodeSourcery