Hi Andy, On May 21 22:36, Andy Polyakov wrote: > Speaking of documentation:-) Is cygwin memory layout documented > somewhere? What I'm trying to ask is if you can provide a pointer. If > it's documented in commentary section in source code, then could you be > so kind to give some approximate directions where to look? A.
It's not exactly documented, no. If you download the sources, there's a file how-cygheap-works.txt, which explains the basics about cygwin's own heap which is inherited to child applications on fork and exec. Other than that, there are just a couple of shared memory areas for various puposes (process list, tape "driver", etc) and the Cygwin DLL itself. The DLL is loaded to 0x61000000, the cygheap is always expected to be right after the end of the DLL's loading area. The shared memory regions have been accidentally loaded to 0x04000000 since 1.5.13 up to current 1.5.16, but will reside beginning at 0x60000000 with the upcoming 1.5.17. If you need more details, you will have to look into the sources, I assume. If you have questions, feel free to send PM, I think more of that is pretty OT for this list. Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat, Inc. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
