From: fche@redhat.com (Frank Ch. Eigler)
To: Stan Shebs <stan@codesourcery.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: [RFC] "actionpoints"?
Date: Mon, 18 Jan 2010 19:35:00 -0000 [thread overview]
Message-ID: <y0mtyujgqai.fsf@fche.csb> (raw)
In-Reply-To: <4B54AC04.7090204@codesourcery.com> (Stan Shebs's message of "Mon, 18 Jan 2010 10:44:20 -0800")
Stan Shebs <stan@codesourcery.com> writes:
>>> 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.k
I don't have a dog in this fight, but how about plain "breakpoint" to
identify any code spot or event where the target process's normal
control flow is broken? In other words, make that the cover term for
naming such abstract locations. Then classify into different possible
breakpoint actions: "stop breakpoint", "trace breakpoint", "watch
breakpoint".
- FChE
prev parent reply other threads:[~2010-01-18 19:35 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
2010-01-18 19:04 ` Pedro Alves
2010-01-21 21:24 ` Daniel Jacobowitz
2010-01-18 19:35 ` Frank Ch. Eigler [this message]
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=y0mtyujgqai.fsf@fche.csb \
--to=fche@redhat.com \
--cc=brobecker@adacore.com \
--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