From: "Eli Zaretskii" <eliz@gnu.org>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: drow@false.org, gdb@sources.redhat.com, mec.gnu@mindspring.com,
rolandz@poczta.fm
Subject: Re: How to setup a breakpoint on constructor
Date: Sun, 18 Jul 2004 05:05:00 -0000 [thread overview]
Message-ID: <9003-Sun18Jul2004071107+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040717205225.56BC04B104@berman.michael-chastain.com> (mec.gnu@mindspring.com)
> Date: Sat, 17 Jul 2004 16:52:25 -0400 (EDT)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
>
> > Coincidentally that's what the entire discussion of 1:N breakpoints
> > last year was about but no one has had time to implement it.
>
> Right.
>
> 1:N breakpoints are better than A::A$base(), but it's been 3 years since
> the ctor-breakpoint issue came up, and we don't have anything at all
> yet.
So how about setting a breakpoint on all of the places, like Daniel
suggested?
> But if someone breaks in A::A$base() and then says 'break 1000' to get
> into the middle of the function (which I do a lot), then they would get
> the breakpoint in the wrong copy! So even if we disambiguate the
> names, the 1:N nature of multiple ctors shines through.
Can't we put a breakpoint on all instances in that case as well?
next prev parent reply other threads:[~2004-07-18 4:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-17 23:17 Michael Elizabeth Chastain
2004-07-18 5:05 ` Eli Zaretskii [this message]
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
-- 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 10:09 Michael Elizabeth Chastain
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=9003-Sun18Jul2004071107+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).