This is the mail archive of the
mailing list for the Archer project.
Re: systemtap markers and gdb
- From: Phil Muldoon <pmuldoon at redhat dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: Project Archer <archer at sourceware dot org>
- Date: Thu, 13 Jan 2011 15:53:25 +0000
- Subject: Re: systemtap markers and gdb
- References: <email@example.com>
- Reply-to: pmuldoon at redhat dot com
Tom Tromey <firstname.lastname@example.org> 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
> 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