[issue5330] profile and cProfile do not report C functions called with keyword arguments

Antoine Pitrou added the comment: Committed in r73064, r73065, r73066, r73067. Thanks! -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue5330] profile and cProfile do not report C functions called with keyword arguments

Antoine Pitrou added the comment: Updated patch, with test. -- nosy: +pitrou Added file: http://bugs.python.org/file14122/issue5330.patch ___ Python tracker ___ _

[issue5330] profile and cProfile do not report C functions called with keyword arguments

Changes by Antoine Pitrou : -- stage: -> patch review versions: +Python 2.7, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list ma

[issue5330] profile and cProfile do not report C functions called with keyword arguments

Changes by Georg Brandl : -- assignee: -> nbastin nosy: +nbastin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue5330] profile and cProfile do not report C functions called with keyword arguments

Changes by Georg Brandl : -- priority: -> critical ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue5330] profile and cProfile do not report C functions called with keyword arguments

Hagen Fürstenau added the comment: I found the reason for this problem: C function calls with keyword arguments follow a different path than those without keywords in the function "call_function" of ceval.c. They end up being handled by "do_call", but there the call is not wrapped by C_TRACE, so

[issue5330] profile and cProfile do not report C functions called with keyword arguments

New submission from Hagen Fürstenau : A C function or method call without keyword arguments gets reported by the profiler as expected (in the line with "{method 'sort' of 'list' object}"): >>> cProfile.run("[].sort()") 4 function calls in 0.000 CPU seconds Ordered by: standard name