From: Stan Shebs <stan@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Stan Shebs <stan@codesourcery.com>, gdb@sourceware.org
Subject: Re: [RFC] "actionpoints"?
Date: Mon, 18 Jan 2010 18:44:00 -0000 [thread overview]
Message-ID: <4B54AC04.7090204@codesourcery.com> (raw)
In-Reply-To: <20100118064348.GA1914@adacore.com>
Joel Brobecker wrote:
>> One of the issues that has come up regularly in our tracepoint work
>> is what GDB's messages to the user should say when they are
>> referring to various combinations of tracepoints and breakpoints.
>>
>
> I like the idea of having a term that means either breakpoint/watchpoint/
> tracepoint, etc. How about "eventpoint"? "actionpoint" sounds OK to me too.
>
"eventpoint" is a good candidate. Googling shows it in VxWorks and the
old VAX/VMS debugger - and a couple dozen appearances in GDB sources(!);
most likely inherited from HP code, which was partly written by ex-DEC
people... To me "eventpoint" has a slight downside in that it is used
in several OS debugging/monitoring tools, tied to various notions of
system-level "event", so the manual would have to emphasize that our
notion of eventpoint is not OS-related in any way. But that doesn't
seem too difficult to explain.
Stan
next prev parent reply other threads:[~2010-01-18 18:44 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
2010-01-18 18:44 ` Stan Shebs [this message]
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=4B54AC04.7090204@codesourcery.com \
--to=stan@codesourcery.com \
--cc=brobecker@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