Process map and fork problems

[Achim Gratz]

Achim Gratz <Stromeko <at> NexGo.DE> writes:
> I'm chasing a problem on some 32bit Windows installs that supposedly
> happened after one of the Windows updates (and probably other software
> updates) in the last few months (the affected users were unable to pin it
> down further unfortunately).  It's obviously caused by two heap sections in
> the process map that are smack dab in the middle of the address range used
> by rebase:
> 
> 20000000-200A0000 rw-p 00000000 0000:0000 0                   [heap]
> 200A0000-38000000 ===p 000A0000 0000:0000 0                   [heap]
> 
> These do not exist on 32bit Cygwin installs on 64bit Windows installations,
> so I couldn't see these problems on my test machine.

On the 64bit Windows installations two eerily similar heap sections appear
much higher in the process image:

80000000-80070000 rw-p 00000000 0000:0000 0                   [heap]
80070000-98000000 ===p 00070000 0000:0000 0                   [heap]

Hm....  why would something like that move from 2GB down to 0.5GB?

Regards,
Achim.


--
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