public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: systemtap markers and gdb
Date: Thu, 13 Jan 2011 15:53:00 -0000	[thread overview]
Message-ID: <m34o9c94wa.fsf@redhat.com> (raw)
In-Reply-To: <m3wrm8g6eb.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu, 13 Jan 2011 08:39:08 -0700")

Tom Tromey <tromey@redhat.com> writes:

> Sergio and I are working on letting gdb stop when a systemtap static
> marker is hit.
>
> I thought I would post the documentation for the user-facing bits for
> comments.
>
> The diff below is missing a little context.  The main new command is:
>
>     catch marker PROVIDER NAME
>
> Let me know what you think.

Why the catch syntax, and not just an addition to the linespec code so
that we can just set regular breakpoints on them?  It would be neat then
to interface with the upcoming condition/action python code. 

(Though I guess in mediation, though we have no catchpoint support in
the Python API at present, there is no reason that we cannot at some
point).

Cheers

Phil

  reply	other threads:[~2011-01-13 15:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 15:39 Tom Tromey
2011-01-13 15:53 ` Phil Muldoon [this message]
2011-01-13 16:06   ` Tom Tromey
2011-01-13 17:15     ` Roland McGrath
2011-01-13 17:38       ` Tom Tromey
2011-02-04 22:00         ` Tom Tromey
2011-02-04 23:45           ` Roland McGrath
2011-02-07 15:22             ` Tom Tromey
2011-02-07 18:41               ` Roland McGrath
2011-02-07 16:55           ` 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=m34o9c94wa.fsf@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=archer@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).