Re:C stdlib isn't threadsafe and even safe Rust didn't save us
by account42 on Thursday January 23, 2025 @06:36AM
(#42803021)
Because it doesn't actually solve anything: You're still replacing whatever getenv returned from under the nose the program code - if that happens in another thread or in a signal handler in the same thread doesn't make any difference.
And that's before you even get to the `extern char *environ` global.
And that's before you even get to the `extern char *environ` global.