X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 10 Dec 2010 10:35:04 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: 1.7.7 - OpenSSH Fatal Error 1114 Message-ID: <20101210093504.GC25347@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20101201161647 DOT GA30913 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20101201161647.GA30913@calimero.vinschen.de> 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: 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 Hi John, On Dec 1 17:16, Corinna Vinschen wrote: > 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. Can you please test the latest developer snapshot from http://cygwin.com/snapshots/? It contains yet another patch which is supposed to workaround this problem. It would be nice if you could report back quickly. Thanks in advance, 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