From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Stan Shebs <stan@codesourcery.com>,
Joel Brobecker <brobecker@adacore.com>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFC] "actionpoints"?
Date: Mon, 18 Jan 2010 19:08:00 -0000 [thread overview]
Message-ID: <201001181908.41355.pedro@codesourcery.com> (raw)
In-Reply-To: <4B54AE21.1070205@codesourcery.com>
On Monday 18 January 2010 18:53:21, Stan Shebs wrote:
> As a small quasi-data-point, in my tracepoint tinkering, I noticed that
> once breakpoints and tracepoints were merged, I drifted into the habit
> of doing "info b" even when I'm only wanting to see the list of
> tracepoints. That might just be because the list has tended to be
> short, only around five action/event/x/*points in all; I imagine that
> filtering by type gets more interesting at 10 and up, as happens with
> rbreak and the like.
Same here.
I've always missed a way to get a list of _only_
breakpoints (points in the program where execution should break),
not including watchpoints, catchpoints, whatnot. I'm now wishing
more for this ever since we merged tracepoints and breakpoints.
Another missing functionality I often miss is way to delete
all breakpoints, but _only_ breakpoints --- leave watchpoints,
tracepoints, etc.
Note:
"delete breakpoints" - deletes everything (breakpoints, tracepoints,
watchpoints, whatnot).
"delete tracepoints" - deletes only tracepoints.
There's no "delete watchpoints", for example.
I find this inconsistenty confusing. If we could have
a new "delete actionpoints" command, we could re-alias "delete" to
delete all kinds of action points, and then have "delete
breakpoints" delete only breakpoints.
--
Pedro Alves
next prev parent reply other threads:[~2010-01-18 19:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 0:22 Stan Shebs
2010-01-16 7:57 ` Eli Zaretskii
2010-01-18 16:51 ` Stan Shebs
2010-01-18 18:08 ` Eli Zaretskii
2010-01-16 13:51 ` Frank Ch. Eigler
2010-01-18 17:09 ` Stan Shebs
2010-01-18 6:44 ` Joel Brobecker
2010-01-18 17:54 ` Eli Zaretskii
2010-01-18 18:18 ` Joel Brobecker
2010-01-18 18:53 ` Stan Shebs
2010-01-18 19:08 ` Pedro Alves [this message]
2010-01-18 18:44 ` Stan Shebs
2010-01-18 19:04 ` Pedro Alves
2010-01-21 21:24 ` Daniel Jacobowitz
2010-01-18 19:35 ` Frank Ch. Eigler
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=201001181908.41355.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=stan@codesourcery.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