Skip to content

gh-122029: Do not unpack method for legacy tracing anymore #130898

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

Merged
merged 3 commits into from
Mar 11, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions Lib/test/test_sys_setprofile.py
Original file line number Diff line number Diff line change
Expand Up @@ -511,6 +511,27 @@ class B:
]
)

# Test CALL_FUNCTION_EX
events = []
sys.setprofile(lambda frame, event, args: events.append(event))
# Not important, we only want to trigger INSTRUMENTED_CALL_KW
args = (1,)
m = B().f
m(*args, key=lambda x: 0)
sys.setprofile(None)
# The last c_call is the call to sys.setprofile
# INSTRUMENTED_CALL_FUNCTION_EX has different behavior than the other
# instrumented call bytecodes, it does not unpack the callable before
# calling it. This is probably not ideal because it's not consistent,
# but at least we get a consistent call stack (no unmatched c_call).
self.assertEqual(
events,
['call', 'return',
'call', 'return',
'c_call'
]
)


if __name__ == "__main__":
unittest.main()
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
:func:`sys.setprofile` and :func:`sys.settrace` will not generate a ``c_call`` event for ``INSTRUMENTED_CALL_FUNCTION_EX`` if the callable is a method with a C function wrapped, because we do not generate ``c_return`` event in such case.
13 changes: 0 additions & 13 deletions Python/legacy_tracing.c
Original file line number Diff line number Diff line change
Expand Up @@ -121,19 +121,6 @@ sys_profile_call_or_return(
Py_DECREF(meth);
return res;
}
else if (Py_TYPE(callable) == &PyMethod_Type) {
// CALL instruction will grab the function from the method,
// so if the function is a C function, the return event will
// be emitted. However, CALL event happens before CALL
// instruction, so we need to handle this case here.
PyObject* func = PyMethod_GET_FUNCTION(callable);
if (func == NULL) {
return NULL;
}
if (PyCFunction_Check(func)) {
return call_profile_func(self, func);
}
}
Py_RETURN_NONE;
}

Expand Down
Loading