]> git.ipfire.org Git - thirdparty/Python/cpython.git/commitdiff
[3.12] Fix typo in perf profiling docs (GH-112112) (#112117)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Wed, 15 Nov 2023 15:48:04 +0000 (16:48 +0100)
committerGitHub <noreply@github.com>
Wed, 15 Nov 2023 15:48:04 +0000 (15:48 +0000)
Fix typo in perf profiling docs (GH-112112)
(cherry picked from commit 0cfdd6e3d17fee8c1c1f4b42b2146abcb43aa34b)

Co-authored-by: Ryuji Tsutsui <ryu22e+github@gmail.com>
Doc/howto/perf_profiling.rst

index af7b67d20429502f23f8c19223dce4df9da695a6..bb1c00e0aa51d5f210f14f42022aff1f0fc88df0 100644 (file)
@@ -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.