public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, pkoning@equallogic.com
Cc: carlton@bactrian.org, gdb@sources.redhat.com
Subject: Re: breakpoints in constructors
Date: Wed, 30 Apr 2003 04:36:00 -0000	[thread overview]
Message-ID: <200304300436.h3U4aRGX025659@duracef.shout.net> (raw)

Can I de-lurk for a minute?

gcc 2.95.3 had a single object code function for each constructor,
with a hidden flag to indicate its "in-charge-ness".  I always thought
that was much nicer for debugging.

But gcc 3.X's multi-object-code implementation is mandated by the
multi-vendor ABI, which will make it harder.

I missed the beginning of this thread so someone's probably already
brought up these points, my apologies if I'm rehashing obvious stuff.

Michael C

             reply	other threads:[~2003-04-30  4:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30  4:36 Michael Elizabeth Chastain [this message]
2003-04-30  5:20 ` Daniel Berlin
  -- strict thread matches above, loose matches on Subject: below --
2005-12-15 14:06 Breakpoints " Amit Kale
2005-12-26  7:52 ` Amit Kale
2005-12-27  4:07   ` Jim Blandy
2003-04-30 14:44 breakpoints " Michael Elizabeth Chastain
2003-05-01  2:13 ` Daniel Berlin
2003-04-18 20:04 David Carlton
2003-04-24 14:50 ` Daniel Jacobowitz
2003-04-24 22:02   ` Paul Koning
2003-04-25  0:30     ` Daniel Jacobowitz
2003-04-29 20:45   ` Paul Koning
2003-04-29 21:24     ` Daniel Jacobowitz
2003-04-30 19:04       ` Michael Eager
2003-04-30 19:11         ` Paul Koning
2003-04-30 19:19         ` 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=200304300436.h3U4aRGX025659@duracef.shout.net \
    --to=mec@shout.net \
    --cc=carlton@bactrian.org \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=pkoning@equallogic.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).