### Version v22.2.0 ### Platform Linux AS-ZISU 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux ### Subsystem _No response_ ### What steps will reproduce the bug? ```console > cat index.mjs import {setTimeout} from 'node:timers/promises' await setTimeout(1000000) > node --experimental-permission --allow-fs-read=\* --inspect-brk index.mjs (node:398141) ExperimentalWarning: Permission is an experimental feature (Use `node --trace-warnings ...` to show where the warning was created) [1] 398141 segmentation fault node --experimental-permission --allow-fs-read=\* --inspect-brk index.mjs ``` The content of the script does not matter - even an empty script will work. ### How often does it reproduce? Is there a required condition? No condition required. Node v22.2.0 will crash everytime when `--experimental-permission` is combined with `--inspect-brk`. ### What is the expected behavior? Why is that the expected behavior? The inspector should work and do not segfault. ### What do you see instead? The node process crash because of segfault. Also, no stack trace is printed. ### Additional information The experimental process-based permission model have unexpected side effects with inspector, which is not well-documented. When enabled, `--inspect` and SIGUSR1 both wouldn't work. Should this be a feature, or another bug?