Sampling profiler fails to display user-defined function in IDLE when started with the run command

Bug report

Bug description:

This is my simple test running IDLE at profiler startup (sudo as I'm running on a Mac, YMMV):

sudo -E ./python.exe -m profiling.sampling run -a --realtime-stats -d 99999 --live -m idlelib

As expected, I can also attach to a running IDLE session:

sudo -E ./python.exe -m profiling.sampling attach -a --realtime-stats -d 99999 --live <PID>

The two versions display things differently. If I attach to a running IDLE, define fib(), then call it with a large n (say, 200), it will run for a while before returning a result. I can see the recursive calls to fib in the display.

If I use the run command instead, I never see fib show in the display. Instead, I see something like this:

It appears all the samples in fib are credited to Misc.mainloop. I know the function is executing, given that small-n calls return quickly with the correct result, but shouldn't fib show up in the display when called with a large value for n if I use the run command to start IDLE?

CPython versions tested on:

CPython main branch

Operating systems tested on:

macOS

按照描述使用遞迴的 fib() 呼叫，重現針對 idlelib 的 profiling.sampling run 命令與 attach 命令之間的差異。首先追蹤 profiling.sampling 如何處理 run 路徑，並將其顯示的樣本與 attach 進行比較；當 fib 等使用者定義的函式出現在 run 顯示中，而不是被歸因於 Misc.mainloop 時，即表示完成。