From: Paul Hilfinger <hilfingr@EECS.Berkeley.EDU>
To: Cyrille Comar <comar@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: [RFC] multiple breakpoints from FILE:LINE
Date: Sun, 15 Jan 2006 22:23:00 -0000 [thread overview]
Message-ID: <200601152223.k0FMNMQ7017374@tully.CS.Berkeley.EDU> (raw)
In-Reply-To: Message from Cyrille Comar <comar@adacore.com> of "Sun, 15 Jan 2006 02:51:36 +0100." <43C9AAA8.2030605@adacore.com>
Cyrille Comar writes:
> I believe it would be worthwhile to have 2 different break commands:
> - break
> - break-multiple (or whatever other more appropriate name)
>
> break-multiple would have the semantics advocated by Daniel (break
> automatically on all relevant locations)
But then 'break', being the shorter and more familiar command name,
would appear from a user's point of view to be the effective default.
If you put a breakpoint in the middle of an inline function (or an Ada
generic procedure or C++ template class method), it seems rather odd
for the default to be "break on one at random" [well, OK; that's what
it is in regular GDB now, but currently there is no alternative, so
there is no choice about defaults]. So if you went the distinct-
command route, you'd probably want 'break' and 'break-single' (er, or
something), the latter being a seldom-chosen specialized command that
would present a menu. Another alternative is a new settable variable.
Paul Hilfinger
next prev parent reply other threads:[~2006-01-15 22:23 UTC|newest]
Thread overview: 31+ 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
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-15 17:38 David Anderson
2006-01-15 17:50 ` Daniel Jacobowitz
2006-01-15 17:54 ` Robert Dewar
2006-01-15 18:33 ` Andreas Schwab
2006-01-15 19:06 ` Robert Dewar
2006-01-13 10:42 Paul Hilfinger
2006-01-13 11:32 ` Eli Zaretskii
2006-01-13 11:56 ` Joel Brobecker
2006-01-13 13:05 ` Eli Zaretskii
2006-01-13 14:17 ` Andrew STUBBS
2006-01-13 15:27 ` Daniel Jacobowitz
2006-01-13 15:25 ` Daniel Jacobowitz
2006-01-13 15:19 ` Paul Koning
2006-01-13 15:23 ` Daniel Jacobowitz
2006-01-13 15:40 ` Joel Brobecker
2006-01-14 10:15 ` Paul Hilfinger
2006-01-14 16:16 ` Daniel Jacobowitz
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=200601152223.k0FMNMQ7017374@tully.CS.Berkeley.EDU \
--to=hilfingr@eecs.berkeley.edu \
--cc=comar@adacore.com \
--cc=gdb@sourceware.org \
/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