Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Reply-To:	Cygwin List <cygwin AT cygwin DOT com>
Message-Id:	<6.0.1.1.0.20040206111932.038ddf78@127.0.0.1>
X-Sender:
Date:	Fri, 06 Feb 2004 11:20:06 -0500
To:	peda AT sectra DOT se, Cygwin List <cygwin AT cygwin DOT com>
From:	Larry Hall <cygwin-lh AT cygwin DOT com>
Subject:	Re: Segfault in _cygwin_dll_entry
In-Reply-To:	<OF17440943.002DACB0-ONC1256E32.002AA005@dbs.sectra.se>
References:	<OF17440943 DOT 002DACB0-ONC1256E32 DOT 002AA005 AT dbs DOT sectra DOT se>
Mime-Version:	1.0

At 02:57 AM 2/6/2004, peda AT sectra DOT se you wrote:
>Larry Hall wrote:
>
>>I'd suggest 'cygcheck cygggi-2.dll'.  Make sure there's no MS CRT in
>>there anywhere.  If there is, you're on dangerous ground.  Comparing the
>>output of this with that of cygii-0.dll might be instructive too.
>
>~$ cygcheck /bin/cyggg-0.dll
>C:/cygwin/bin/cyggg-0.dll
>  C:/cygwin/bin\cygwin1.dll
>    C:\WINNT\system32\ADVAPI32.DLL
>      C:\WINNT\system32\NTDLL.DLL
>      C:\WINNT\system32\KERNEL32.DLL
>      C:\WINNT\system32\RPCRT4.DLL
>
>~$ cygcheck /bin/cyggii-0.dll
>C:/cygwin/bin/cyggii-0.dll
>  C:/cygwin/bin\cygwin1.dll
>    C:\WINNT\system32\ADVAPI32.DLL
>      C:\WINNT\system32\NTDLL.DLL
>      C:\WINNT\system32\KERNEL32.DLL
>      C:\WINNT\system32\RPCRT4.DLL
>  C:/cygwin/bin\cyggg-0.dll
>
>~$ cygcheck /bin/cygggi-2.dll
>C:/cygwin/bin/cygggi-2.dll
>  C:/cygwin/bin\cyggg-0.dll
>    C:/cygwin/bin\cygwin1.dll
>      C:\WINNT\system32\ADVAPI32.DLL
>        C:\WINNT\system32\NTDLL.DLL
>        C:\WINNT\system32\KERNEL32.DLL
>        C:\WINNT\system32\RPCRT4.DLL
>  C:/cygwin/bin\cyggii-0.dll


OK, fine.


>>>Is it a known problem?
>
>>No.  If nothing "obvious" turns up in your initial efforts to scope the
>>problem, you're probably going to be best off debugging into the Cygwin
>>DLL to see where it crashes.
>
>What should I read to get going with debugging into the Cygwin DLL?


Start here:

<http://cygwin.com/contrib.html>



--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -