strange crashes on invocation
Fri Oct 1 22:03:00 GMT 2010
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?
>> 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.
>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
>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
So: How about how?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin