X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Fri, 1 Oct 2010 18:02:55 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: strange crashes on invocation
Message-ID: <20101001220255.GA1694@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <4C9B8AC6.9080808@budcat.com> <4C9BB392.9070802@budcat.com> <4C9BE120.1080701@budcat.com> <20100924091712.GA18898@calimero.vinschen.de> <4C9CD24C.1000606@budcat.com> <20100924165747.GB5793@calimero.vinschen.de> <4C9CECB4.1040607@budcat.com> <20100924195422.GA27380@ednor.casa.cgf.cx> <4CA0B8D3.8020801@budcat.com> <4CA0CBBC.2060202@budcat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4CA0CBBC.2060202@budcat.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Mon, Sep 27, 2010 at 11:52:12AM -0500, Heath Kehoe wrote:
>
>
>On 9/27/2010 10:31 AM, Heath Kehoe wrote:
>> On 9/24/2010 2:54 PM, Christopher Faylor wrote:
>>> On Fri, Sep 24, 2010 at 01:23:48PM -0500, Heath Kehoe wrote:
>>>> Well, another difference is the addition of PATH_MAX*2 bytes on the
>>>> stack. Those functions do some stack manipulations that I'm having
>>>> trouble grokking. Does 'ret' need to be topmost on the stack?
>>>>
>>>> As a test, I moved the 'ret' definition after that of 'dll_path' (in
>>>> std_dll_init). So far with that change, I have not seen the LoadLibrary
>>>> fatal error, though I need to test it more to be sure.
>>> I've moved some other stuff around in that function.  Could you try
>>> the latest CVS?
>>>
>>> cgf
>>>
>> With your changes, I have not yet encountered any of the error 998
>> failures, and I've run a couple of rebuilds of my project as a stress-test.
>>
>> Thanks,
>> -h
>
>Ugh! spoke too soon. It happened again:
>
>       1 [main] bash 5112! C:\cygwin\bin\bash.exe: *** fatal error - 
>could not load C:\Windows\system32\ws2_32.dll, Win32 error 998
>Stack trace:
>Frame     Function  Args
>00288974  6102740B  (00288974, 00000000, 00000000, 00000000)
>00288C64  6102740B  (61179C40, 00008000, 00000000, 6117B997)
>00289C94  61004B2B  (6117B084, 00289CB0, 00000000, 00000000)
>00289EE4  6100136E  (61053A2A, 00000154, 00000002, 00000002)
>
>It's definitely a lot less frequent, though.

I truly do not understand why playing with the stack should have
any effect but I've added a retry loop to the LoadLibrary call after
reading some vague MSDN articles which indicated that it could
fail mysteriously.

So:  How about how?

http://cygwin.com/snapshots.html

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

