From: Daniel Jacobowitz <drow@false.org>
To: Cyrille Comar <comar@adacore.com>
Cc: Paul Koning <pkoning@equallogic.com>,
hilfingr@gnat.com, gdb@sourceware.org
Subject: Re: : Re: [RFC] multiple breakpoints from FILE:LINE
Date: Mon, 16 Jan 2006 13:47:00 -0000 [thread overview]
Message-ID: <20060116134731.GB31547@nevyn.them.org> (raw)
In-Reply-To: <43CBA0D7.3000903@adacore.com>
On Mon, Jan 16, 2006 at 02:34:15PM +0100, Cyrille Comar wrote:
> Daniel Jacobowitz wrote:
> >I've yet to see a compelling reason to break on one constructor and not
> >the other. Most users don't even know the difference between when each
> >is called.
>
> I am not familiar at all with C++ debugging, so the situation is not
> clear to me: To break on constructors, do you use the FILE:LINE of the
> class? Wouldn't that break on destructors as well? (or any other type
> specific implicit operation, if such thing exists in C++)
No, you either use Class::Class or Class::~Class, or the FILE:LINE of a
user-provided definition. They all have names whether or not they have
explicit definitions.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-16 13:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 1:51 Cyrille Comar
2006-01-15 16:33 ` Paul Koning
2006-01-15 16:45 ` Daniel Jacobowitz
2006-01-15 17:41 ` Robert Dewar
2006-01-15 22:23 ` Paul Koning
2006-01-16 13:43 ` Cyrille Comar
2006-01-16 13:47 ` Daniel Jacobowitz [this message]
2006-01-16 14:16 ` Cyrille Comar
2006-01-16 15:31 ` Paul Koning
2006-01-15 17:38 ` Robert Dewar
2006-01-16 6:58 ` Jim Blandy
2006-01-16 10:03 ` Robert Dewar
2006-01-16 10:04 ` Robert Dewar
2006-01-15 22:23 ` Paul Hilfinger
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=20060116134731.GB31547@nevyn.them.org \
--to=drow@false.org \
--cc=comar@adacore.com \
--cc=gdb@sourceware.org \
--cc=hilfingr@gnat.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