From: Ryuji Tsutsui Date: Wed, 15 Nov 2023 15:40:19 +0000 (+0900) Subject: Fix typo in perf profiling docs (#112112) X-Git-Tag: v3.13.0a2~76 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=0cfdd6e3d17fee8c1c1f4b42b2146abcb43aa34b;p=thirdparty%2FPython%2Fcpython.git Fix typo in perf profiling docs (#112112) --- diff --git a/Doc/howto/perf_profiling.rst b/Doc/howto/perf_profiling.rst index af7b67d20429..bb1c00e0aa51 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.