Greetings, Ken Brown! > I have one other suggestion: If you rebase because of a fork failure, reboot > before retrying the application that failed. I just had the following > experience:
> I was running emacs on my 32-bit Cygwin installation and got a fork failure > involving /usr/bin/cygMagickCore-6.Q16-2.dll. Windows had loaded this DLL at > a > very low address. I did a full rebase and restarted emacs, but that DLL was > still loaded at a low address, even though rebasing had put the base address > at > a very reasonable 0x6e550000. [You can see where a DLL is loaded in a > process's > address space by examining the file /proc/<PID>/maps.] I then rebooted, > restarted emacs, and verified that the DLL was now loaded at 0x6e550000, as > expected. > I've seen this happen many times. I don't know the explanation, but my guess > is > that Windows does some caching that causes it to try to load a given DLL at > the > same base address as it used the last time that DLL was loaded. Rebooting > clears the cache. Can someone who understands this stuff confirm my guess or > provide a better explanation? prefetch/superfetch ? I normally disable this crap. I can live with boot times 15 seconds longer, and these kinds of services proved to slow down the system over the years at all times, no matter what is claimed in advertising. -- With best regards, Andrey Repin Friday, October 16, 2015 18:40:11 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
