X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org X-VirusChecked: Checked X-Env-Sender: hkehoe AT budcat DOT com X-Msg-Ref: server-11.tower-202.messagelabs.com!1285284130!52982121!1 X-StarScan-Version: 6.2.4; banners=budcat.com,-,- Message-ID: <4C9BE120.1080701@budcat.com> Date: Thu, 23 Sep 2010 18:22:08 -0500 From: Heath Kehoe User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: "cygwin AT cygwin DOT com" Subject: Re: strange crashes on invocation References: <4C9B8AC6 DOT 9080808 AT budcat DOT com> <4C9BB392 DOT 9070802 AT budcat DOT com> In-Reply-To: <4C9BB392.9070802@budcat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 9/23/2010 3:07 PM, Heath Kehoe wrote: > On 9/23/2010 12:13 PM, Heath Kehoe wrote: >> I have a build system that uses rake under cygwin, and every so often >> a build tool will crash on invocation: >> >> 1 [main] bclanc 1576! C:\budcat\tools\bin\bclanc.exe: *** fatal >> error - could not load w, Win32 error 998 >> Stack trace: >> Frame Function Args >> 00289F44 6102740B (00289F44, 00000000, 00000000, 00000000) >> 0028A234 6102740B (61179C20, 00008000, 00000000, 6117B997) >> 0028B264 61004B2B (6117B084, 61163DD0, 00000000, 00000000) >> 0028B4C4 6100137A (61053A9A, 00000168, 00000002, 00000002) > [snip] >> My OS is Win7 x64. Cygwin is built from CVS as of 2010-09-21 12:11 >> (though I'm pretty sure I've seen this on 1.7.7 as well) > I've confirmed that this crash is happening on 1.7.7; it does not appear > to happen on 1.7.6. > > Could it be related to the DLL loading change relating to the security > advisory? I'll probably try to revert the revision 1.171 changes to > autoload.cc to see if that makes any difference. I'm currently testing the latest CVS, but with these changes rolled back: http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/autoload.cc.diff?r1=1.170&r2=1.171&cvsroot=src&f=h Thus far, I have not yet seen the crash. I'll hammer on it more to make sure. BTW, that stack trace's addresses correspond to: cygwin_stackdump cygwin_stackdump __api_fatal std_dll_init Which is unsurprising and also not very informative (I'd already found where the fatal error was coming from by searching for "could not load" in the sources). When looking at the autoload.cc code, I noticed the api_fatal call is still using dll->name as an ascii string when revision 1.171 changed dll->name to a wide string. That's why the error message only prints the first character of the dll name. -h ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ -- 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