From: "Eli Zaretskii" <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: mec.gnu@mindspring.com, gdb@sources.redhat.com, rolandz@poczta.fm
Subject: Re: How to setup a breakpoint on constructor
Date: Mon, 19 Jul 2004 14:51:00 -0000 [thread overview]
Message-ID: <7137-Mon19Jul2004065710+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040718214852.GA30558@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 18 Jul 2004 17:48:53 -0400)
> Date: Sun, 18 Jul 2004 17:48:53 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> Is it one breakpoint with multiple addresses, or have we created multiple
> breakpoints?
The latter, I'd say. After all, that was one of the reasons for the
change in the breakpoint machinery that now supports multiple
locations for a single breakpoint, right?
> If the latter, we have to somehow distinguish the two of them in the UI
> so that the user can see which is which; and generate different
> location strings for them, so that if the user recompiles and reloads
> the breakpoints get set on the same place, in case they have different
> conditions or commands or enable status.
We should do these, true; but even if we didn't, the resulting
deficiencies would be much less painful than the current situation.
AFAIK, bugs in constructors and destructors are quite common, so
having no good means to debug them is BAD, IMHO.
> The general case of 'break <line>' has many similar issues, for
> instance in templates or inlined functions; describing the location is
> quite a problem.
>
> Not an insoluble one, surely, but I get stuck every time I work on
> it...
Maybe describing the issues here could produce some usefule discusion
about possible design solutions.
next prev parent reply other threads:[~2004-07-19 3:58 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
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 [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 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=7137-Mon19Jul2004065710+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