This is the mail archive of the
mailing list for the Cygwin project.
Re: References to both cygwin1.dll and msvcrt.dll
- From: Patrick Samson <p_samson at yahoo dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 27 Sep 2004 06:38:41 -0700 (PDT)
- Subject: Re: References to both cygwin1.dll and msvcrt.dll
--- Igor Pechtchanski wrote:
> On Mon, 27 Sep 2004, Patrick Samson wrote:
> > I use a dll which have references to both
> > cygwin and m$:
> > $ cygcheck /usr/share/tcl8.4/dp4.0/win/dp40.dll
> > D:/cygwin/usr/share/tcl8.4/dp4.0/win/dp40.dll
> > D:\cygwin\bin\tcl84.dll
> > C:\WINNT\System32\ADVAPI32.DLL
> > C:\WINNT\System32\ntdll.dll
> > C:\WINNT\System32\KERNEL32.dll
> > C:\WINNT\System32\USER32.dll
> > C:\WINNT\System32\GDI32.dll
> > C:\WINNT\System32\RPCRT4.dll
> > D:\cygwin\bin\cygwin1.dll <-------------
> > C:\WINNT\System32\msvcrt.dll <------------
> > C:\WINNT\System32\WS2_32.DLL
> > C:\WINNT\System32\WS2HELP.dll
> > Should I suspect this to be a possible source of
> trouble? Or does it
> > mean nothing?
> Depends. Usually, this results in some sort of
> trouble, mostly because of
> the separate parallel stdio, malloc, etc
> implementations. You may be able
> to get away with it for a while if none of the
> msvcrt functions are
> actually called, but it may come back and bite you
> in the future.
Since my post I found a way to reproduce on
development the problem I have on production.
At some point cygserver hits 100%CPU and Postgres
backends are no more able to serve requests.
Now I must narrow the number of components involved,
to prove that the culprit is really this DLL.
As you suggest, it may be a mess with mem alloc.
Corina, any hint?
May I expect some useful info with log or debug
options to cygserver?
Do you Yahoo!?
Declare Yourself - Register online to vote today!
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html