sys.setprofile and equivalent C API don't track all callable C code

Bug report

Bug description:

import sys
import mmap

def prof(frame, event, arg):
    print(event, arg)

sys.setprofile(prof)

x = mmap.mmap(-1, 10_000)
open("/dev/null")

When run with Python 3.13 on Linux:

c_call <built-in function open>
call None
call None
return None
return None
c_return <built-in function open>
return None

No mention of mmap.mmap(), perhaps because it's a constructor of a type object.

(This is really an issue with the underlying C API, PyTrace_C_CALL is similarly not happening.)

As someone doing profiling, this means that any code running inside C type constructors is invisible, which is problematic and means I'm going to have to change how one of my profilers works.

CPython versions tested on:

3.12, 3.13

Operating systems tested on:

Linux

Reproduisez l’exemple Linux avec sys.setprofile, mmap.mmap() et open(), puis suivez le chemin de profiling autour de PyTrace_C_CALL et des constructeurs de types C. Comparez les événements observés avec la visibilité attendue du code C appelable ; le travail est terminé lorsque l’activité pertinente des constructeurs est signalée de manière cohérente par sys.setprofile et l’API C équivalente.