At 02:57 AM 2/6/2004, [EMAIL PROTECTED] 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/