Mail Archives: cygwin/2009/11/21/14:26:55
On Sat, Nov 21, 2009 at 08:16:29AM -0500, mike marchywka wrote:
>On 11/21/09, Corinna Vinschen wrote:
>>No, never. If there is a concurrency problem with the envionment, it's
>>between threads of the same process. In that case, we can make getenv,
>>setenv and friends thread-safe, but it's still actually a problem of
>>the application, given that getenv, setenv and friends are not
>>thread-safe per POSIX. See
>>http://www.opengroup.org/onlinepubs/9699919799/functions/setenv.html
>>http://www.opengroup.org/onlinepubs/9699919799/functions/getenv.html
>>http://www.opengroup.org/onlinepubs/9699919799/functions/unsetenv.html
>>
>
>well, the question was somewhat rhetorical/disingenuous but I don't see
>how in the general case then the OS can allow two simultaneous
>processes to modify windoze env variables in a way that corrupts them.
>The app is responsible for itself but I'm not sure what it can do with
>respect to other processes. If you wanted an emulation layer to be
>safe you are still limited by the OS( but you may have already known
>that LOL).
I am beginning to think that this is a troll. Corinna talks about
threads and you talk about processes. Either you're clueless about the
distinction or you are just "having fun".
There are simple things that can be done to make Cygwin's handling of
environment variables thread safe. Stop arguing about it. You're just
looking stupid now.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -