From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/29832] New: probe python.function.entry does not get hits (while .return does)
Date: Mon, 28 Nov 2022 12:31:44 +0000 [thread overview]
Message-ID: <bug-29832-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29832
Bug ID: 29832
Summary: probe python.function.entry does not get hits (while
.return does)
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
Target Milestone: ---
With both systemtap-4.8-1.fc38 and the upstream git commit
342e5ec5619066f227ff9c3a5c,
probe python.function.entry isn't getting hits, while respective .return prob
gets hit just fine:
# cat test.py
import random, time
print(random.random())
time.sleep(3)
# stap -we 'probe process("/usr/lib*/libpython*.so*").mark("function__return")
{filename = user_string($arg1); if (filename =~ "random") {println(filename)
exit()}}' -c 'python3 ./test.py >/dev/null'
/usr/lib64/python3.11/random.py
# stap -we 'probe process("/usr/lib*/libpython*.so*").mark("function__entry")
{filename = user_string($arg1); if (filename =~ "random") {println(filename)
exit()}}' -c 'python3 ./test.py >/dev/null'
#
#
This is with python3-3.11.0-1.fc38.x86_64.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-11-28 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 12:31 mcermak at redhat dot com [this message]
2022-12-12 12:11 ` [Bug runtime/29832] " mcermak at redhat dot com
2022-12-12 12:22 ` mcermak at redhat dot com
2022-12-13 9:28 ` mcermak at redhat dot com
2022-12-13 16:22 ` mcermak at redhat dot com
2022-12-14 8:31 ` mcermak at redhat dot com
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=bug-29832-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).