From: Paul Gilliam <pgilliam@us.ibm.com>
To: gdb@sources.redhat.com
Subject: Re: breakpoints in C++ constructors
Date: Tue, 14 Sep 2004 19:38:00 -0000 [thread overview]
Message-ID: <200409141235.42478.pgilliam@us.ibm.com> (raw)
In-Reply-To: <vt2fz5k6dic.fsf@zenia.home>
On Tuesday 14 September 2004 09:06, Jim Blandy wrote:
-- snip --
> Daniel has done some work on the breakpoint code to
-- snip --
> The original intention was to extend this to allow a single user
> > breakpoint to cover multiple machine-code locations, but that change
> hasn't been made yet: the code still assumes a one-to-one
> relationship. Completing this would be the natural way to support
> constructor breakpoints.
If one breakpoint could cover multiple machine-code locations, then that
mechanizm could be use for the requested new "break at all functions"
command.
-=# Paul Gilliam #=-
prev parent reply other threads:[~2004-09-14 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 16:07 Jim Blandy
2004-09-14 16:15 ` Daniel Jacobowitz
2004-09-14 19:16 ` Andrew Cagney
2004-09-15 0:06 ` Paul Koning
2004-09-16 19:17 ` Jim Blandy
2004-09-14 19:38 ` Paul Gilliam [this message]
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=200409141235.42478.pgilliam@us.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=gdb@sources.redhat.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