Fix typo in perf profiling docs (#112112)

This commit is contained in:
Ryuji Tsutsui 2023-11-16 00:40:19 +09:00 committed by GitHub
parent 422c0f0301
commit 0cfdd6e3d1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -97,7 +97,7 @@ Then we can use ``perf report`` to analyze the data:
| | | | | |--2.97%--_PyObject_Malloc | | | | | |--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 (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 functions use the same C function to evaluate bytecode so we cannot know which Python function corresponds to which
bytecode-evaluating function. bytecode-evaluating function.