X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 2 Mar 2012 09:59:43 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygheap base mismatch detected
Message-ID: <20120302085943.GB14404@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4F4E7CC8 DOT 9090804 AT cwilson DOT fastmail DOT fm> <20120301105139 DOT GF2257 AT calimero DOT vinschen DOT de> <CAB8Xom9nR9g=R_uzzZM5D+OHZ3wQhkJ+F5tAKBL0xL60iTc9rA AT mail DOT gmail DOT com> <20120301121442 DOT GG2257 AT calimero DOT vinschen DOT de> <4F4FFBD8 DOT 1080803 AT cwilson DOT fastmail DOT fm>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4F4FFBD8.1080803@cwilson.fastmail.fm>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

On Mar  1 17:44, Charles Wilson wrote:
> On 3/1/2012 7:14 AM, Corinna Vinschen wrote:
> > Hmm.  cygcheck loads the Cygwin DLL dynamically.  It does not depend on
> > any other Cygwin distro DLL.  But it's started from a Cygwin parent.  So
> > the loaded CYgwin DLL checks the layout just like it had been linked
> > against.  And apparently it gets rebased at load time.  Which means to
> > me, there's another DLL already loaded into the process at an address
> > which overlaps with the address space the Cygwin DLL should have been
> > loaded to.
> > 
> > So I guess you just have to find out what is the cause for rebasing
> > the Cygwin DLL.  Try VMMap from sysinternals with a cygcheck -svr piped
> > into less, so that you can easily observe the process in vmmap.
> 
> It appears to be C:\WINDOWS\SysWOW64\PGHook.dll which is part of Avecto
> Privilege Guard (which could certainly be classed as a BLODA IMO; thank
> you paranoid corporate IT policies...).
> 
> For cygcheck, PGHook.dll gets loaded at its desired image base:
> 
> $ objdump -p /c/Windows/syswow64/pghook.dll |grep ImageBase
> ImageBase               61100000
> 
> So, it appears that for normal cygwin processes, PGHook gets rebased
> elsewhere, and cygwin "wins."  For instance, /bin/top.exe -> PGHook gets
> loaded at 01FD000, b/c cygwin1.dll is already at 0x61000000.  OTOH,
> there's nothing in the cygcheck.exe process that prevents PGHook from
> getting its desired base addr -- which then conflicts with cygwin's
> desired base addr when it is (later) dynloaded.
> 
> Is there some workaround that could be used? It's not as if cygcheck is

Rebase pghook.dll.  Call "cmd /c cygcheck".

> really trying to initialize and *use* cygwin1.dll facilities, is it? So,
> perhaps cygwin1.dll/dcrt0 could ignore the fact that it has been
> rebased, when dynamically loaded? (or perhaps, only when dynloaded by
> some app named 'cygcheck.exe').

That's kind of tricky.  When the DLL is loaded into the wrong address,
then there are pointers in the processes startupinfo which potentially
point into nirvana.  That affects any process.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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