From: Jim Ingham <jingham@apple.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc breakpoint] Catch exceptions
Date: Wed, 26 Mar 2003 22:49:00 -0000 [thread overview]
Message-ID: <36D88DD8-5FDD-11D7-B2F4-00039379E320@apple.com> (raw)
In-Reply-To: <200303261748.h2QHmKr16829@duracef.shout.net>
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
next prev parent reply other threads:[~2003-03-26 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 17:48 Michael Elizabeth Chastain
2003-03-26 22:49 ` Jim Ingham [this message]
[not found] <1048606641.15061.ezmlm@sources.redhat.com>
2003-03-25 23:51 ` Jim Ingham
2003-03-26 0:03 ` Daniel Jacobowitz
2003-03-26 2:14 ` 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=36D88DD8-5FDD-11D7-B2F4-00039379E320@apple.com \
--to=jingham@apple.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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