You're correct. Parent comment is inaccurate. The problem is that a different library in the same process can use getenv without locking (or without locking the

You're correct. Parent comment is inaccurate. The problem is that a different library in the same process can use getenv without locking (or without locking the same lock as your code)