This is the mail archive of the cygwin-patches mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH RFC] fork: reduce chances for "address space is already occupied" errors


On Mar 28 10:17, Michael Haubenwallner wrote:
> As it is not some other dll being loaded at the colliding adress: any
> idea how to find out _what_ is allocated there (in the forked child),
> to find out whether we can reserve these areas even more early?

I'm not sure what addresses you're talking about ATM.  The addresses in
the 0x4:00000000 - 0x6:00000000 range?  These are the interesting ones.
The relocation to some random low address should only occur if there's
a collision in this range.

I'm not quite sure how to find out what happens, unless you stop the
process in reserve_space and inspect the memory layout with sysinternal's
vmmap tool:

https://docs.microsoft.com/en-us/sysinternals/downloads/vmmap


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

Attachment: signature.asc
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]