From: Stan Cox <scox@redhat.com>
To: Craig Ringer <craig@2ndquadrant.com>, systemtap@sourceware.org
Cc: "Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: Emitting marker names instead of hex statement addresses for SDT probes?
Date: Tue, 19 Jan 2021 17:21:40 -0500 [thread overview]
Message-ID: <7de6169c-2235-4022-6fad-f07f0edadfa0@redhat.com> (raw)
In-Reply-To: <CAMsr+YFZPEPqS+qoPNLTd3q8gBs9f29nXMd5k4Ouzhj8G5RSkg@mail.gmail.com>
If I use --dyninst (which creates a probe source that is easy to modify
and rebuild to try quick experiments) then this change forces the probe
point name:
#define STP_NEED_PROBE_NAME=1
changed in enter_dyninst_uprobe:
c->probe_point = sup->probe->pn; /* was ->pp */
% stapdyn *.so -c /work/scox/stap/sdt/tstclass.x
process("/work/scox/stap/sdt/tstclass.x").mark("test_probe_4") aa=0xa
string1=abc
10 20 abc xyz
10 20 abc xyz
(where the original probe was doing: printf("%s aa=%#lx
string1=%s\n",pp(),@cast($arg1,"struct A")->aa, ...)
next prev parent reply other threads:[~2021-01-19 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 4:49 Craig Ringer
2021-01-19 22:21 ` Stan Cox [this message]
2021-01-21 5:47 ` Craig Ringer
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=7de6169c-2235-4022-6fad-f07f0edadfa0@redhat.com \
--to=scox@redhat.com \
--cc=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).