This is the mail archive of the cygwin 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: Windows 10 updates causes fork retry no child processes

Gerry Reno writes:
> I think the simplest way for right now might be to have a batch file
> run at startup that runs rebaseall.
> Something like these lines in a batch file:
> cd C:\Cygwin\bin
> .\ash /bin/rebaseall
> This would rebase the dlls each time after Windows Update forces a reboot.
> Do you see any issue with that?

You are barking up the wrong tree.  If the Cygwin installation is
unchanged (as you said it is), then each rebaseall will result in
exactly the same base addresses for the DLL as before.  So yes, you
could do what you say (provided that you didn't start any services that
start Cygwin processes), but it wouldn't help anything.

If your Cygwin installation is too big to fit into the address space
(likely if it's a 32bit installation and you installed everything), then
you need to trim it down.  If it's a 32bit Windows, you'll also need to
switch to a 3GB user VM so the heap gets moved above 2GB.  If it's
BLODA, you need to stop using it or configure it to stay out of Cygwin's
business.  The thing that _does_ change each reboot is that any DLL
using ASLR will end up in a different place until the next reboot, so
unless you check which DLL you collide with (if it is indeed a collision
and not an intercept), you'll always get a different Cygwin DLL name

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:

Problem reports:
Unsubscribe info:

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