cygcheck triggers Wow6432Node infinite loop on Windows Server 2008

Andy Koppe andy.koppe@gmail.com
Wed Jun 24 21:38:00 GMT 2009


2009/6/24 GJ Hagenaars:
> Hi there,
>
> On a Windows Server 2008, running cronbug from the (bash) command line
> results in an ever increasing cronbug.txt file because cygcheck walks the
> registry and gets into an infinite loop.
>
> It will repeatedly find these entries, deeper and deeper in the registry:
> Cygnus Solutions
> Cygnus Solutions\Cygwin
> Cygnus Solutions\Cygwin\mounts v2
> Cygnus Solutions\Cygwin\mounts v2\/
> Cygnus Solutions\Cygwin\mounts v2\/usr/bin
> Cygnus Solutions\Cygwin\mounts v2\/usr/lib
> Cygnus Solutions\Cygwin\Program Options
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygnus Solutions
> HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Wow6432Node\Cygnus Solutions
> HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Wow6432Node\Wow6432Node\Cygnus
> Solutions
> HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Wow6432Node\Wow6432Node\Wow6432Node\Cygnus
> Solutions
>
>
> Wow6432Node is Windows-on-windows, and allows registry entries for 32 bit
> applications to be stored along side registry entries for 64 bit
> applications of the same name (allowing for different entries for 64 bit and
> 32 bit apps).  The infinite loop behaviour is known and "fixed" by Microsoft
> by making the registry key HKLM\Software\Wow6432Node hidden from
> RegEnumKeyEx in the 32 bit hive.

Gah. Why oh why can't Microsoft ever create an elegant and
straightforward solution to anything? "Program Files (x86)", "Windows
on Windows 64", "Wow6432Node", 64-bit DLLs in "System32", and 32-bit
DLLs in "SysWOW64". This is all so ugly and confusing that you have to
wonder whether they're not deliberately trying to obfuscate stuff.

Andy

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



More information about the Cygwin mailing list