From: Tom Tromey <tromey@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, frysk@sourceware.org
Subject: Re: patch to add breakpoint commands
Date: Wed, 05 Mar 2008 18:03:00 -0000 [thread overview]
Message-ID: <18382.54075.736457.76675@fleche.redhat.com> (raw)
In-Reply-To: <47CEDB6F.2090301@redhat.com>
Andrew> for all of these they have several things:
[...]
Andrew> - should the end result be to stop or continue (attribute or not?)
For this I don't see much wrong with the gdb model -- stop by default,
let the command specify "go" if it wants. This has never caused me
much trouble (while OTOH I frequently forget 'silent').
Andrew> that can be characterised as attributes; as, dare I suggest,
Andrew> you're reading into the intent of the HPD, the way to do this
Andrew> is would be with -silent option to the commands that create
Andrew> and edit (see actions) actionpoints.
Yeah, that would be fine by me.
Tom
prev parent reply other threads:[~2008-03-05 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 16:39 Tom Tromey
2008-03-05 17:42 ` Andrew Cagney
2008-03-05 18:03 ` Tom Tromey [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=18382.54075.736457.76675@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).