-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent behavior for sys.monitoring.events.CALL
#116626
Comments
Yes, |
markshannon
pushed a commit
that referenced
this issue
Mar 13, 2024
gaogaotiantian
added a commit
to gaogaotiantian/cpython
that referenced
this issue
Mar 13, 2024
…_FUNCTION_EX` (pythonGH-116627) (cherry picked from commit 8332e85) Co-authored-by: Tian Gao <[email protected]>
markshannon
pushed a commit
that referenced
this issue
Mar 14, 2024
Closing because the PR has been merged and backported. Please re-open if there's more needed here. |
vstinner
pushed a commit
to vstinner/cpython
that referenced
this issue
Mar 20, 2024
adorilson
pushed a commit
to adorilson/cpython
that referenced
this issue
Mar 25, 2024
diegorusso
pushed a commit
to diegorusso/cpython
that referenced
this issue
Apr 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Bug description:
According to the docs,
CALL
event should be emitted as long as there's a function call in Python code. However,CALL_FUNCTION_EX
does it differently - it only emits the event when it's a call to C function. So monitoring the following code produce different results:I think we should just fix
CALL_FUNCTION_EX
to make it work the same as the other CALL instructions.CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux
Linked PRs
CALL
events for allINSTRUMENTED_CALL_FUNCTION_EX
#116627CALL
events for all `INSTRUMENTED_CALL_FUNCT… #116732The text was updated successfully, but these errors were encountered: