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
This is always a race condition; if you hit this line your code has a fatal design flaw. The same pid could have been reallocated by the kernel, and you would end up sending the signal to an unrelated process.
This is always a race condition; if you hit this line your code has a fatal design flaw. The same pid could have been reallocated by the kernel, and you would end up sending the signal to an unrelated process.
What if the PID is user-supplied? What if I’m running as PID 1 in my own PID namespace and can guarantee PID allocation behavior? I expect to be able to handle a nonexistent PID gracefully.
zig/lib/std/os.zig
Line 482 in aa61e03
Is there a way users are expected to handle this? Seems like there's no way to entirely avoid this branch when calling the function
The text was updated successfully, but these errors were encountered: