Greetings, Erik Bray! > Thanks for the reply. The issue here isn't getting the Windows > process environment--that can be done, albeit trickily [1]. While > it's true there are security implications, in this case that is > handled at the OpenProcess call required to obtain a handle to the > process. It's true you can't just read the environment from a process > you don't have permission to.
> The issue here though is reading the Cygwin process's environment > which is separate from its Windows environment, and the above > technique is inapplicable. Update Windows environment block when Cygwin environment is updated. -- With best regards, Andrey Repin Tuesday, November 29, 2016 19:26:20 Sorry for my terrible english... -- 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
