Yet another rebase/ASLR/fork case (sorry)

[Alex]

Hi,

I am trying to install cygwin on a computer which has McAfee antivirus and Windows 7 (6.1.7601 Service Pack 1 Build 7601).

I am aware that cygwin needs to be able to keep its DLLs in the same address in order for fork to work etc and have read various threads on it. In my case, I have made sure the scanner doesn't interfere with Cygwin by adding it to exclusions list. I even used regedit.exe to confirm and indeed I see value "**\cygwin\**" under:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\McAfee\SystemCore\VSCore\On Access Scanner\McShield\Configuration\Default\WxcludeItem_5

I have also seen on the on-access scan window that when installing / running cygwin the "last scan file" is never shows anything under c:\cygwin, so that seems to work.

Even so, I still get the fork errors. I tried to fix it, with a fresh boot and making sure nothing (bash.exe or whatever) is running I opened "dash.exe" and tried to run the failing post-install scripts by hand:

--

$ /etc/postinstall/0p_000_autorebase.dash

creating empty /var/cache/rebase/rebase_pkg

      0 [main] dash 1980 fork: child 13048 - died waiting for dll loading, errno 11

--

I tried running "./rebaseall" but got the same results:

--

$ ./rebaseall

$ /etc/postinstall/0p_000_autorebase.dash

creating empty /var/cache/rebase/rebase_pkg

      0 [main] dash 12664 fork: child 11832 - died waiting for dll loading, errno 11

/bin/rebaselst: 98: /bin/rebaselst: Cannot fork

--

Finally I tried to get an exchaustive list of shared libraries to do this:

---

$ ./find /bin /lib /usr -iname '*.so' > /tmp/to_rebase.lst

$ ./find /bin /lib /usr -iname '*.dll' >> /tmp/to_rebase.lst

$ /bin/rebaseall -T /tmp/to_rebase.lst

--

        NOTE: removed "/bin/cyglsa64.dll" and "/usr/bin/cyglsa64.dll" from to_rebase.lst before running rebasealll -T

Still no luck. Whenever I try to run the post-install scripts to fix the installation, they fail...

Any suggestions on what to do? Unfortunately this is a work PC and I cannot disable McAfee altogether, but the idea was that we have that exclusion so that it doesn't cause this sort of issue...

Thanks for any feedback