public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: patch to add breakpoint commands
Date: Wed, 05 Mar 2008 17:42:00 -0000	[thread overview]
Message-ID: <47CEDB6F.2090301@redhat.com> (raw)
In-Reply-To: <18382.49031.893322.680963@fleche.redhat.com>

Tom Tromey wrote:
> Here's a patch that adds breakpoint commands.  I recommend not
> committing it, because it is ugly, but I thought I'd post it so folks
> can see what needs to be done.
>
> Problems with this:
>
> * I really wanted to give commands a "-silent" option (I never liked
>   gdb's "'silent' is a magical first command" thing) -- but doing this
>   would mean hooking into BreakpointCommand.
>   

I have to agree; hpd describes this entire group as "actionpoints" and 
lists:

- breakpoints
- watchpoints
- barrier

and we've suggestions for additions such as:

- catch syscall
- catch dlopen (?)
- catch signal
- catch fork
- catch clone
- catch exec

for all of these they have several things:

- the commands to run when the event is triggered
- should the hit be verbose or silent
- should the end result be to stop or continue (attribute or not?)
- ?

that can be characterised as attributes; as, dare I suggest, you're 
reading into the intent of the HPD, the way to do this is would be with  
-silent option to the commands that create and edit (see actions) 
actionpoints.

Andrew



  reply	other threads:[~2008-03-05 17:42 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 [this message]
2008-03-05 18:03   ` Tom Tromey

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=47CEDB6F.2090301@redhat.com \
    --to=cagney@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=tromey@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).