From 91ee5a0d598606ecef107d65dd85098ada634d80 Mon Sep 17 00:00:00 2001 From: Ryuji Tsutsui Date: Thu, 16 Nov 2023 00:40:19 +0900 Subject: [PATCH] Fix typo in perf profiling docs (GH-112112) (cherry picked from commit 0cfdd6e3d17fee8c1c1f4b42b2146abcb43aa34b) Co-authored-by: Ryuji Tsutsui --- Doc/howto/perf_profiling.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/howto/perf_profiling.rst b/Doc/howto/perf_profiling.rst index af7b67d2042950..bb1c00e0aa51d5 100644 --- a/Doc/howto/perf_profiling.rst +++ b/Doc/howto/perf_profiling.rst @@ -97,7 +97,7 @@ Then we can use ``perf report`` to analyze the data: | | | | | |--2.97%--_PyObject_Malloc ... -As you can see, the Python functions are not shown in the output, only ``_Py_Eval_EvalFrameDefault`` +As you can see, the Python functions are not shown in the output, only ``_PyEval_EvalFrameDefault`` (the function that evaluates the Python bytecode) shows up. Unfortunately that's not very useful because all Python functions use the same C function to evaluate bytecode so we cannot know which Python function corresponds to which bytecode-evaluating function.