From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14002 invoked by alias); 26 Mar 2003 22:49: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 13989 invoked from network); 26 Mar 2003 22:49:35 -0000 Received: from unknown (HELO mail-out1.apple.com) (17.254.0.52) by sources.redhat.com with SMTP; 26 Mar 2003 22:49:35 -0000 Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.12.8/8.12.8) with ESMTP id h2QMnZOr022070 for ; Wed, 26 Mar 2003 14:49:35 -0800 (PST) Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Wed, 26 Mar 2003 14:49:27 -0800 Received: from apple.com (inghji.apple.com [17.201.22.240]) by scv1.apple.com (8.11.3/8.11.3) with ESMTP id h2QMnYt16787; Wed, 26 Mar 2003 14:49:34 -0800 (PST) Date: Wed, 26 Mar 2003 22:49:00 -0000 Subject: Re: [rfc breakpoint] Catch exceptions Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) Cc: gdb-patches@sources.redhat.com To: Michael Elizabeth Chastain From: Jim Ingham In-Reply-To: <200303261748.h2QHmKr16829@duracef.shout.net> Message-Id: <36D88DD8-5FDD-11D7-B2F4-00039379E320@apple.com> Content-Transfer-Encoding: 7bit X-SW-Source: 2003-03/txt/msg00534.txt.bz2 Yeah, the Apple gcc folks made it so that all the [in-charge] and [not-in-charge] etc versions of constructors & destructors funnel back into a single function, then we just make sure gdb breaks on that one when it goes to break on the constructor. It looks a little odd, 'cause you have this weirdo extra stack frame that you don't understand, but at least it works. Dunno if they ever submitted that hack back to the FSF, however. If they did, the gdb side was pretty trivial. Jim On Wednesday, March 26, 2003, at 09:48 AM, Michael Elizabeth Chastain wrote: > Hi Jim, > >> BTW. The more general problem of a symbol resolving to multiple >> instances - for instance setting file:line breakpoints in inlined >> functions or template method defn's - is something we need to address. >> It really ticks off our C++ friends. > > And with gcc 3, it happens with constructors and destructors, because > the compiler emits multiple object code functions for each constructor > and each constructor. This shows up multiple times in the PR database, > which means many users are unhappy with it. > > Just another voice of gloom, > > Michael C > -- Jim Ingham jingham@apple.com Developer Tools Apple Computer