From: Stan Shebs <stan@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
stan@codesourcery.com, gdb@sourceware.org
Subject: Re: [RFC] "actionpoints"?
Date: Mon, 18 Jan 2010 18:53:00 -0000 [thread overview]
Message-ID: <4B54AE21.1070205@codesourcery.com> (raw)
In-Reply-To: <20100118181819.GN5800@adacore.com>
Joel Brobecker wrote:
>>> I don't think we should change all the user interface (eg: info
>>> breakpoints") where it is already clear what the output is about.
>>>
>> ??? How is it clear? "info break" displays all ``actionpoints''
>> regardless of their kind, last time I tried. Am I missing something?
>>
>
> Yeah, well, the command is misnamed. We can introduce aliases and
> do a gradual transition, if we want.
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.
Stan
next prev parent reply other threads:[~2010-01-18 18:53 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 [this message]
2010-01-18 19:08 ` Pedro Alves
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=4B54AE21.1070205@codesourcery.com \
--to=stan@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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