Skip to content

Commit 91ee5a0

Browse files
ryu22emiss-islington
authored andcommitted
Fix typo in perf profiling docs (pythonGH-112112)
(cherry picked from commit 0cfdd6e) Co-authored-by: Ryuji Tsutsui <ryu22e+github@gmail.com>
1 parent 1445d77 commit 91ee5a0

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

Doc/howto/perf_profiling.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ Then we can use ``perf report`` to analyze the data:
9797
| | | | | |--2.97%--_PyObject_Malloc
9898
...
9999
100-
As you can see, the Python functions are not shown in the output, only ``_Py_Eval_EvalFrameDefault``
100+
As you can see, the Python functions are not shown in the output, only ``_PyEval_EvalFrameDefault``
101101
(the function that evaluates the Python bytecode) shows up. Unfortunately that's not very useful because all Python
102102
functions use the same C function to evaluate bytecode so we cannot know which Python function corresponds to which
103103
bytecode-evaluating function.

0 commit comments

Comments
 (0)