X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<4A4269D4.4000508@hagenaars.com>
References:	<4A4269D4 DOT 4000508 AT hagenaars DOT com>
Date:	Wed, 24 Jun 2009 21:12:29 +0100
Message-ID:	<416096c60906241312l40255adeof56898bea5af24de@mail.gmail.com>
Subject:	Re: cygcheck triggers Wow6432Node infinite loop on Windows Server 2008
From:	Andy Koppe <andy DOT koppe AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

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\Wow6432No=
de\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). =C2=A0The infinite loop behaviour is known and "fixed" by M=
icrosoft
> 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

- Raw text -