This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: strange crashes on invocation
On Sep 24 11:31, Heath Kehoe wrote:
>
> On 9/24/2010 4:17 AM, Corinna Vinschen wrote:
> >
> >Can you revert to the latest from CVS and try again with this patch applied:
> >
> >Index: autoload.cc
> >===================================================================
> >RCS file: /cvs/src/src/winsup/cygwin/autoload.cc,v
> >retrieving revision 1.174
> >diff -u -p -r1.174 autoload.cc
> >--- autoload.cc 23 Sep 2010 20:18:16 -0000 1.174
> >+++ autoload.cc 24 Sep 2010 09:15:40 -0000
> >@@ -233,7 +233,7 @@ std_dll_init ()
> > dll->handle = h;
> > }
> > else if (!(func->decoration& 1))
> >- api_fatal ("could not load %W, %E", dll->name);
> >+ api_fatal ("could not load %W, %E", dll_path);
> > else
> > dll->handle = INVALID_HANDLE_VALUE;
> > }
> >
> >If the error occurs again, what is the path printed in the error
> >message? Is it sane? Does the directory correspond to your local
> >X:\Windows\System32 directory?
> >
>
> Done. The crash came back and here's the result:
>
> 1 [main] bclanc 2544! C:\budcat\tools\bin\bclanc.exe: ***
> fatal error - could not load C:\Windows\system32\ws2_32.dll, Win32
> error 998
Thanks for testing.
> The path is correct. I have no explanation why changing from a
> filename to a pathname (and LoadLibrary to LoadLibraryW) would make
> any difference, unless there's a race condition, say if
> LoadLibrary[W] is a bit faster when you give it a full path.
That doesn't make sense. It's the LoadLibraryW call itself which is
failing with error 998, "Invalid access to memory location".
Hmm. Puzzeling.
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