This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Setting values in library tapsets from user tapscript?
- From: Craig Ringer <craig at 2ndquadrant dot com>
- To: "Frank Ch. Eigler" <fche at redhat dot com>
- Cc: systemtap at sourceware dot org
- Date: Mon, 13 Jan 2020 14:42:13 +0800
- Subject: Re: Setting values in library tapsets from user tapscript?
- References: <CAMsr+YE+e_N4tfeUvUZxapkNPfy5_8=kN_VKWgM0piG3jC_1HA@mail.gmail.com> <87y2x1eucp.fsf@redhat.com>
On Thu, 31 Oct 2019 at 06:34, Frank Ch. Eigler <fche@redhat.com> wrote:
>
> craig wrote:
>
> > Related to my earlier post, is there any way to supply macro values to
> > referenced tapsets? [...]
>
> Yeah, indirectly. [...]
- create a new foo.stpm file in a new directory /zoo
>
>
Apologies for the late reply. That did the trick. The Makefile for the
relevant programs now generates a templated .stpm that defines appropriate
macros. Then a regular tapset uses those macros in a probe alias. So the
tapscripts using the tapset don't have to care. The invoker supplies the
correct include path and it works.
It'd be good to be able to resolve @var etc against userspace modules as
discussed before, but it can be worked around this way at least.
--
Craig Ringer http://www.2ndQuadrant.com/
2ndQuadrant - PostgreSQL Solutions for the Enterprise