X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 1 Dec 2010 17:16:47 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.7 - OpenSSH Fatal Error 1114
Message-ID: <20101201161647.GA30913@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <AANLkTi=_9mQFewkE7wYj4OtR3X3NJs8qVXgM5jdx=3Do AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <AANLkTi=_9mQFewkE7wYj4OtR3X3NJs8qVXgM5jdx=3Do@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
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 Dec  1 07:13, John Fano wrote:
> Hi Everyone,
> 
> I have cygwin 1.7.7 installed on a win2003 r2 file server.  
> [...]
> 4: '      0 [main] sshd 1388 C:\\cygwin\\usr\\sbin\\sshd.exe: ***
> fatal error - could not load u, Win32 error 1114\nStack
                              ^^^
    It's probably safe to assume that this is user32.dll.
    There's a glitch in the debug output in 1.7.7.
			      
The difference between Cygwin 1.7.5 and 1.7.7 is just that 1.7.7 loads
the dynamically loaded system DLLs using the full path, while 1.7.5
loads them using just the name, for instance:

  1.7.5:   LoadLibrary ("user32.dll")
  1.7.7:   LoadLibrary ("C:\\Windows\\System32\\user32.dll")

The reason we're doing that is
http://www.microsoft.com/technet/security/advisory/2269637.mspx

So far we have not the faintest idea why loading the system DLLs using
the full path fails in some scenarios, while using just the DLL name
works.

There's some kind of a workaround in the current development sources,
but apparently this solution also doesn't provide a 100% success rate.

Anyway, can you try if this effect still occurs with the latest
developer snapshot from http://cygwin.com/snapshots/, please?


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