From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: jimb@redhat.com, mec.gnu@mindspring.com
Cc: drow@false.org, eliz@gnu.org, gdb@sources.redhat.com, rolandz@poczta.fm
Subject: Re: How to setup a breakpoint on constructor
Date: Sat, 17 Jul 2004 10:09:00 -0000 [thread overview]
Message-ID: <20040716221532.0708C4B104@berman.michael-chastain.com> (raw)
jimb> If I remember right, the use of separate complete and base
jimb> constructors is an ABI requirement; the compiler doesn't have the
jimb> option of just generating whatever code it likes.
The ABI does require separate names.
If I recall correctly, Apple implemented this by having separate names
for base ctor and complete ctor (as required by the ABI) and then having
them call a unified constructor.
Gcc optimization can reduce calls from {base,complete}-ctor to
unified-ctor, from call instructions to jump instructions.
Then the debugger just puts ctor breakpoints on the
unified-ctor.
http://gcc.gnu.org/ml/gcc-patches/2002-08/msg00354.html
Apple folks, have I got that right?
Michael C
next reply other threads:[~2004-07-16 22:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-17 10:09 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-18 19:29 Michael Elizabeth Chastain
2004-07-19 3:58 ` Eli Zaretskii
2004-07-17 23:17 Michael Elizabeth Chastain
2004-07-18 5:05 ` Eli Zaretskii
2004-07-18 18:44 ` Daniel Jacobowitz
2004-07-18 19:03 ` Eli Zaretskii
2004-07-19 3:22 ` Daniel Jacobowitz
2004-07-19 14:51 ` Eli Zaretskii
2004-07-16 19:59 Michael Elizabeth Chastain
2004-07-16 22:15 ` Jim Blandy
2004-07-17 14:30 ` Eli Zaretskii
2004-07-17 14:54 ` Daniel Jacobowitz
2004-07-15 13:55 Michael Elizabeth Chastain
2004-07-15 14:09 ` Daniel Jacobowitz
2004-07-16 11:11 ` Eli Zaretskii
2004-07-16 14:27 ` Daniel Jacobowitz
2004-07-17 10:30 ` Eli Zaretskii
2004-07-15 11:31 Michael Elizabeth Chastain
2004-07-16 13:17 ` Roland Zerek
2004-07-15 10:30 Roland Zerek
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=20040716221532.0708C4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=rolandz@poczta.fm \
/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