From: Daniel Jacobowitz <drow@false.org>
To: Paul Koning <pkoning@equallogic.com>
Cc: comar@adacore.com, hilfingr@gnat.com, gdb@sourceware.org
Subject: Re: : Re: [RFC] multiple breakpoints from FILE:LINE
Date: Sun, 15 Jan 2006 16:45:00 -0000 [thread overview]
Message-ID: <20060115164459.GA5390@nevyn.them.org> (raw)
In-Reply-To: <17354.31047.417000.385481@gargle.gargle.HOWL>
On Sun, Jan 15, 2006 at 11:33:11AM -0500, Paul Koning wrote:
> Cyrille> I believe it would be worthwhile to have 2 different break
> Cyrille> commands: - break - break-multiple (or whatever other more
> Cyrille> appropriate name)
>
> Cyrille> break-multiple would have the semantics advocated by Daniel
> Cyrille> (break automatically on all relevant locations)
>
> Cyrille> break, instead of presenting a menu, would issue an error of
> Cyrille> the kind:
>
> Cyrille> (gdb) break FILENAME:LINENUM multiple choices for this
> Cyrille> breakpoint, please use any of the following: break-multiple
> Cyrille> FILENAME:LINENUM break FILENAME:instance1.function:LINENUM
Well, I think this should be just one command, and maybe have "break"
in the CLI issue a warning (just like it does now). But that's a
relatively small change.
The instance1.function syntax handles one important Ada case, but
there's plenty of other cases; for instance, there can be an arbitrary
chain of inlining. I'm not convinced that there's any practical way to
get it right.
> Nice. What syntax would you use for the two constructors, and three
> destructors, that have the same C++ names?
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.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-15 16:45 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 [this message]
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
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=20060115164459.GA5390@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