You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Measure starting a program that needs an interpreter
openkal-linux could not start one AT ALL --- every `#!` script on every
architecture --- and no suite anywhere looked, which is why it survived until a
foreign binary made the same failure loud on aarch64.
⚠️ THIS IMPLEMENTATION IS EXPECTED TO PASS AND IS CHECKED ANYWAY. It has no
`execveat': it enters the directory and calls `execve' with a whole path, so the
kernel never holds a name the interpreter cannot reopen. That is a reason to
BELIEVE it works. Believing is exactly how the other one went unmeasured, and
the reasoning that said "not ours" there was three true observations pointing
the wrong way.
Test-only; no behaviour changes and no version bump.
0 commit comments