From: Tom Tromey <tromey@redhat.com>
To: pmuldoon@redhat.com
Cc: Project Archer <archer@sourceware.org>
Subject: Re: systemtap markers and gdb
Date: Thu, 13 Jan 2011 16:06:00 -0000 [thread overview]
Message-ID: <m3k4i8g545.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m34o9c94wa.fsf@redhat.com> (Phil Muldoon's message of "Thu, 13 Jan 2011 15:53:25 +0000")
Phil> Why the catch syntax, and not just an addition to the linespec code so
Phil> that we can just set regular breakpoints on them? It would be neat then
Phil> to interface with the upcoming condition/action python code.
We considered this but decided on catchpoints for two reasons.
First, we wanted to expose the marker arguments somehow. Adding special
behavior to breakpoints for one kind of linespec seemed ugly.
Second, linespec.c is already too gross.
It occurs to me now that I don't know how we'll support letting the user
view the marker arguments outside of "commands". Maybe instead of a
special convenience function we should just set a bunch of convenience
variables, or a single array-valued convenience variable.
Phil> (Though I guess in mediation, though we have no catchpoint support in
Phil> the Python API at present, there is no reason that we cannot at some
Phil> point).
Yeah, we will want to do that as part of this work.
Tom
next prev parent reply other threads:[~2011-01-13 16:06 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
2011-01-13 16:06 ` Tom Tromey [this message]
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=m3k4i8g545.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=pmuldoon@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).