From: Craig Ringer <craig@2ndquadrant.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: Newbie Notes
Date: Sun, 10 Nov 2019 05:05:00 -0000 [thread overview]
Message-ID: <CAMsr+YERz2wB1U2NZUN1+mXmhPbrBgOZx0AGN5Ui7yEVMTCCXQ@mail.gmail.com> (raw)
In-Reply-To: <20191108120338.GA22271@redhat.com>
On Fri, Nov 8, 2019, 20:03 Frank Ch. Eigler <fche@redhat.com> wrote:
> Hi -
>
> > Aha. Makes sense.
> >
> > I can work around the PATH issues with @var etc by generating a .tapm
> > script with the paths templated in, then use that in a tapset that
> defines
> > the probe aliases etc.
> >
> > That'll work well enough that I think I can prepare a usable tapset for
> > PostgreSQL.
>
> And if that tapset is in a tapset directory, then the unused var
> warnings won't be an issue.
>
Yep. When I clean up my probes into a tapset I'll post about it here.
>
> > > OK, working on this bug.
> >
> > Cool. I dug through a fair bit of code without figuring it out, sorry :S
> > Want me to open a github issue?
>
> Nah, already fixed it last night. (We use sourceware.org/bugzilla.)
>
Wow, thanks. Pulling to have a look.
> > [...]
> > I'll be stuck being backward compatible for a while so I had to work
> around
> > it anyway...
>
> Fair enough. When we release a new version, we do plop it onto as
> many old platform versions as we can. So fedora30 etc. should get it,
> within a few weeks.
>
Very nice!
My work actually runs our own package distribution system now too, so if we
needed to we could even build and ship systemtap.
Which reminds me, I need to tweak our packages to force the installation of
debuginfo.
>
> - FChE
>
>
prev parent reply other threads:[~2019-11-10 5:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 7:19 Craig Ringer
2019-10-28 8:55 ` Craig Ringer
2019-10-30 20:10 ` Frank Ch. Eigler
2019-10-31 14:01 ` Craig Ringer
2019-11-07 18:52 ` Frank Ch. Eigler
2019-11-08 4:15 ` Craig Ringer
2019-11-08 12:03 ` Frank Ch. Eigler
2019-11-10 5:05 ` Craig Ringer [this message]
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=CAMsr+YERz2wB1U2NZUN1+mXmhPbrBgOZx0AGN5Ui7yEVMTCCXQ@mail.gmail.com \
--to=craig@2ndquadrant.com \
--cc=fche@redhat.com \
--cc=systemtap@sourceware.org \
/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).