From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19672 invoked by alias); 26 Mar 2003 00:03:59 -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 19664 invoked from network); 26 Mar 2003 00:03:59 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 26 Mar 2003 00:03:59 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18y0I5-0007lN-00; Tue, 25 Mar 2003 20:05:21 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18xyOY-0003bx-00; Tue, 25 Mar 2003 19:03:54 -0500 Date: Wed, 26 Mar 2003 00:03:00 -0000 From: Daniel Jacobowitz To: Jim Ingham Cc: gdb-patches@sources.redhat.com Subject: Re: [rfc breakpoint] Catch exceptions Message-ID: <20030326000354.GA13823@nevyn.them.org> Mail-Followup-To: Jim Ingham , gdb-patches@sources.redhat.com References: <1048606641.15061.ezmlm@sources.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2003-03/txt/msg00508.txt.bz2 On Tue, Mar 25, 2003 at 03:51:32PM -0800, Jim Ingham wrote: > One thing we had to worry about at least on Mac OS X is that we don't > use a shared libstdc++, rather every shlib that uses C++ get its own > copy of all the libsupc++ code. So there are actually many copies of > __cxa__begin_catch hanging around. To do this properly, you have to > search exhaustively for these symbols, not just take the first hit. > Moreover, you have to redo it on every shared library load, or you will > miss some. This still might bite you on other systems, for instance if > out of paranoia somebody had linked their shlib or executable > statically to libstdc++.a (so they wouldn't get bit by changing ABI > issues or whatever). > > 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. I thought I was going to have > time to think about this in the next month or two, but I got > sidetracked on other issues. But I will need to get back to it after > our WWDC (in June). Yes. Rather than focusing on it with a special hack here, I'd rather eventually address it properly. Thanks for pointing this out. > I thought from some comments in other notes that this was something you > were thinking about as well, Daniel. Is that true? I'm interested in the problem, but like everyone I have a dreadful shortage of time :( -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer