X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 24 Jun 2009 15:30:47 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygcheck triggers Wow6432Node infinite loop on Windows Server 2008 Message-ID: <20090624193047.GA1472@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4A4269D4 DOT 4000508 AT hagenaars DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A4269D4.4000508@hagenaars.com> User-Agent: Mutt/1.5.19 (2009-01-05) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Wed, Jun 24, 2009 at 02:00:52PM -0400, GJ Hagenaars wrote: >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. > >http://msdn.microsoft.com/en-us/library/ms724072(VS.85).aspx > > >Many registry cleaners are (still) struggling with this, as are registry >backup utilities, and also, it appears, cygcheck. Which version of cygcheck is this? Does it come from 1.7 or 1.5? cgf -- 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