From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Ingham <jingham@apple.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc breakpoint] Catch exceptions
Date: Wed, 26 Mar 2003 00:03:00 -0000 [thread overview]
Message-ID: <20030326000354.GA13823@nevyn.them.org> (raw)
In-Reply-To: <B4D17DA2-5F1C-11D7-BFD4-00039379E320@apple.com>
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
next prev parent reply other threads:[~2003-03-26 0:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1048606641.15061.ezmlm@sources.redhat.com>
2003-03-25 23:51 ` Jim Ingham
2003-03-26 0:03 ` Daniel Jacobowitz [this message]
2003-03-26 2:14 ` Jim Ingham
2003-03-26 17:48 Michael Elizabeth Chastain
2003-03-26 22:49 ` Jim Ingham
-- strict thread matches above, loose matches on Subject: below --
2003-03-25 3:01 Daniel Jacobowitz
2003-03-25 16:05 ` Andrew Cagney
2003-03-25 16:14 ` Daniel Jacobowitz
2003-04-27 17:52 ` Daniel Jacobowitz
2003-05-02 0:13 ` David Carlton
2003-05-02 0:25 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030326000354.GA13823@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jingham@apple.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox