From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH v4 3/3] trace-cruncher: Example script for uprobes high level API
Date: Tue, 28 Jun 2022 15:16:21 +0300 [thread overview]
Message-ID: <20220628121621.572506-4-tz.stoyanov@gmail.com> (raw)
In-Reply-To: <20220628121621.572506-1-tz.stoyanov@gmail.com>
Proposed example illustrates how to use uprobes high level API to trace
all functions for user program. It can be attached to already running
program, or run the program and trace its execution.
Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
---
examples/user_trace.py | 39 +++++++++++++++++++++++++++++++++++++++
1 file changed, 39 insertions(+)
create mode 100755 examples/user_trace.py
diff --git a/examples/user_trace.py b/examples/user_trace.py
new file mode 100755
index 0000000..3fdef26
--- /dev/null
+++ b/examples/user_trace.py
@@ -0,0 +1,39 @@
+#!/usr/bin/env python3
+
+"""
+SPDX-License-Identifier: CC-BY-4.0
+
+Copyright 2022 VMware Inc, Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
+"""
+
+import sys
+import shutil
+
+import tracecruncher.ftracepy as ft
+
+if __name__ == "__main__":
+ if len(sys.argv) < 2:
+ print('Usage: ', sys.argv[0], ' [PROCESS or PID]')
+ sys.exit(1)
+
+ # Create new Ftrace instance to work in. The tracing in this new instance
+ # is not going to be enabled yet.
+ inst = ft.create_instance(tracing_on=False)
+
+ # Create a user tracing context for given process, exclude the libraries
+ if sys.argv[1].isdigit():
+ utrace = ft.user_trace(pid=int(sys.argv[1]), follow_libs=False)
+ else:
+ utrace = ft.user_trace(argv=sys.argv[1:], follow_libs=False)
+
+ # Trace execution of all available functions in the given process
+ utrace.add_function(fname="*")
+
+ # Add trace points on functions return as well
+ utrace.add_ret_function(fname="*")
+
+ # Start tracing in an instance
+ utrace.enable(instance=inst, wait=False)
+
+ # Read the trace buffer during the trace until ctrl-c is pressed
+ ft.read_trace(instance=inst)
--
2.35.3
prev parent reply other threads:[~2022-06-28 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 12:16 [PATCH v4 0/3] trace-cruncher: ftrace uprobes support Tzvetomir Stoyanov (VMware)
2022-06-28 12:16 ` [PATCH v4 1/3] trace-cruncher: ftrace uprobe raw API Tzvetomir Stoyanov (VMware)
2022-06-28 12:16 ` [PATCH v4 2/3] trace-cruncher: High level wrappers for ftrace uprobes Tzvetomir Stoyanov (VMware)
2022-06-28 12:16 ` Tzvetomir Stoyanov (VMware) [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=20220628121621.572506-4-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.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 NNTP newsgroup(s).