summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2023-11-15 15:48:04 (GMT)
committerGitHub <noreply@github.com>2023-11-15 15:48:04 (GMT)
commit77f59bf66448c0c0ea73066d4a220276a3fab99d (patch)
treee794909e35b522f07dc0148be4d14bf87c79141c /Doc
parent1445d77282f9082f3fecde772ddf6bb2f5a383f1 (diff)
downloadcpython-77f59bf66448c0c0ea73066d4a220276a3fab99d.zip
cpython-77f59bf66448c0c0ea73066d4a220276a3fab99d.tar.gz
cpython-77f59bf66448c0c0ea73066d4a220276a3fab99d.tar.bz2
[3.12] Fix typo in perf profiling docs (GH-112112) (#112117)
Fix typo in perf profiling docs (GH-112112) (cherry picked from commit 0cfdd6e3d17fee8c1c1f4b42b2146abcb43aa34b) Co-authored-by: Ryuji Tsutsui <ryu22e+github@gmail.com>
Diffstat (limited to 'Doc')
-rw-r--r--Doc/howto/perf_profiling.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/howto/perf_profiling.rst b/Doc/howto/perf_profiling.rst
index af7b67d..bb1c00e 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.