Running the python.exe manually (even without the arguments), I see shared_region: enter(0x64ec414cc8604bf,0x64ec414cdf0b637,0x0,7,0,1): vm_map_enter(0x7fff00000000,0xffe00000,0x64ec414bea8c89f) error 0x3 in the kernel log and no crash dump. The google pointed me to golang/go#895, so I've tried to use dtrace to see what is being done.

dtrace -n 'fbt::vm_shared_region_enter:entry{trace(pid);trace(execname);printf("%xd %xd %xd\n", args[0]->hdr.links.start, args[0]->hdr.links.end, args[0]->size);stack();}' \
       -n 'fbt::vm_shared_region_enter:return{trace(arg0);trace(arg1);}'

returns a few entries and only one is returning 0x3

Details

dtrace: description 'fbt::vm_shared_region_enter:entry' matched 1 probe
dtrace: description 'fbt::vm_shared_region_enter:return' matched 1 probe
CPU     ID                    FUNCTION:NAME
  0 278470     vm_shared_region_enter:entry      6943  zsh                              107692000d 7fffffe00000d 10d0000d
          kernel`vm_map_exec+0x17f
          kernel`0xffffff8019eaf1c0+0x10a7
          kernel`0xffffff8019eb61c0+0x642
          kernel`__mac_execve+0x227
          kernel`execve+0x59
          kernel`unix_syscall64+0x27d
          kernel`hndl_unix_scall64+0x16

0 278471    vm_shared_region_enter:return              3642                3

7 278470     vm_shared_region_enter:entry      6944  zsh                              4000000d 7fffffe00000d 4ba000d
          kernel`vm_map_exec+0x17f
          kernel`0xffffff8019eaf1c0+0x10a7
          kernel`0xffffff8019eb61c0+0x642
          kernel`__mac_execve+0x227
          kernel`execve+0x59
          kernel`unix_syscall64+0x27d
          kernel`hndl_unix_scall64+0x16

7 278471    vm_shared_region_enter:return              3642                0

0 278470     vm_shared_region_enter:entry      6946  zsh                              107f20000d 7fffffe00000d d8000d
          kernel`vm_map_exec+0x17f
          kernel`0xffffff8019eaf1c0+0x10a7
          kernel`0xffffff8019eb61c0+0x642
          kernel`__mac_execve+0x227
          kernel`execve+0x59
          kernel`unix_syscall64+0x27d
          kernel`hndl_unix_scall64+0x16

0 278471    vm_shared_region_enter:return              3642                0

0 278470     vm_shared_region_enter:entry      6949  zsh                              10fb3b000d 7fffffe00000d 121000d
          kernel`vm_map_exec+0x17f
          kernel`0xffffff8019eaf1c0+0x10a7
          kernel`0xffffff8019eb61c0+0x642
          kernel`__mac_execve+0x227
          kernel`execve+0x59
          kernel`unix_syscall64+0x27d
          kernel`hndl_unix_scall64+0x16

0 278471    vm_shared_region_enter:return              3642                0

0 278470     vm_shared_region_enter:entry      6951  zsh                              105b6a000d 7fffffe00000d 45d000d
          kernel`vm_map_exec+0x17f
          kernel`0xffffff8019eaf1c0+0x10a7
          kernel`0xffffff8019eb61c0+0x642
          kernel`__mac_execve+0x227
          kernel`execve+0x59
          kernel`unix_syscall64+0x27d
          kernel`hndl_unix_scall64+0x16

0 278471    vm_shared_region_enter:return              3642                0

2 278470     vm_shared_region_enter:entry      6952  zsh                              10910e000d 7fffffe00000d 45d000d
          kernel`vm_map_exec+0x17f
          kernel`0xffffff8019eaf1c0+0x10a7
          kernel`0xffffff8019eb61c0+0x642
          kernel`__mac_execve+0x227
          kernel`execve+0x59
          kernel`unix_syscall64+0x27d
          kernel`hndl_unix_scall64+0x16

2 278471    vm_shared_region_enter:return              3642                0

4 278470     vm_shared_region_enter:entry      6953  zsh                              105749000d 7fffffe00000d 45d000d
          kernel`vm_map_exec+0x17f
          kernel`0xffffff8019eaf1c0+0x10a7
          kernel`0xffffff8019eb61c0+0x642
          kernel`__mac_execve+0x227
          kernel`execve+0x59
          kernel`unix_syscall64+0x27d
          kernel`hndl_unix_scall64+0x16

So, I guess our python executable doesn't even start, so it's not the Go bug. Then it's something to do with loading of the mach-o files themselves?

Uh oh!

python310 is broken on x86_64-darwin #154120

Description

Metadata

Metadata

Assignees

Labels

Fields

Projects

Milestone

Relationships

Development

Issue actions