Dear Andrey, > The mapping is consistent throughout the execution tree.
I would like to understand the underlying mechanism. The documentation (FAQ section 4.20) states (as far as I understand) that the Windows path of the Cygwin system root an executable sees is the parent directory of the folder in which the cygwin1.dll resides which is loaded by an executable. As I showed, this doesn't seem to be the case. How does it work then? How is the system root folder passed from parent to child? > At best, nothing will work Actually if I put cmd in between and clear a few environment variables it works very well in fairly complicated scenarios. Still I would like to understand how the underlying mechanisms work (preferably without reverse engineering). Best regards, Michael Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -- 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
