X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS,TBC X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 13 Jan 2010 19:21:48 -0500 Message-ID: Subject: Re: Possible BSOD from getcwd on WinXP SP3 From: Robert Pendell To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Wed, Jan 13, 2010 at 10:57 AM, Eric Blake wrote: > Henson, George A CTR USA MEDCOM JMLFDC > writes: > >> >> Hello, >> >> Building tar seems to trigger a Blue Screen Of Death on WinXP. > > Rather, it is triggering a bug in your ntfs.sys driver. =C2=A0Cygwin is a= user app, > and as such, cannot cause a BSOD. =C2=A0Only drivers can do that. > >> The only information I have been able to get out of the Windows crash >> dumps is the fault happens somewhere in the ntfs.sys driver. > > Report this to whoever provided the driver. =C2=A0Meanwhile, you can work= around it > via: > > ./configure gl_cv_func_getcwd_path_max=3Dyes > > to prime the cache and skip that check (I do that anyways on my XP machin= e, in > my /usr/local/share/config.site file, not because my driver is buggy, but > because Microsoft has acknowledged that XP has quadratic handling of long= path > names, and that Vista or newer have linear handling; the quadratic handli= ng > makes the test spin for minutes at 100% CPU utilization, attributable to = system > call churn rather than application action). =C2=A0Also, that check is rep= eated among > tar, coreutils, findutils, and a few other GNU packages. > > And for the record, I've also noticed that sysinternal's procexp can cras= h the > system when trying to examine the run of that particular conftest.exe wit= h very > deep hierarchies. > > -- > Eric Blake > volunteer cygwin tar maintainer > > > > -- > Problem reports: =C2=A0 =C2=A0 =C2=A0 http://cygwin.com/problems.html > FAQ: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 http:= //cygwin.com/faq/ > Documentation: =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://cygwin.com/docs.html > Unsubscribe info: =C2=A0 =C2=A0 =C2=A0http://cygwin.com/ml/#unsubscribe-s= imple > > Something tells me it isn't the ntfs.sys driver causing it anyways. That's just me though. George -- Any chance you might be able to check for and email me the minidump crash files from your windows\minidump folder? You can zip up all of the ones in there and send them to my private email if you like. I'll run them through windows windbg and see what it says the culprit is. I know it won't guarantee that we will find the culprit but we might get close. Eric -- The ntfs.sys driver is 99% of the time stock Windows. There is never any need for a company to provide another ntfs.sys driver file. If the trigger happened it was likely something associated with the file but probably not that file itself. Maybe storage drivers. Robert Pendell shinji AT elite-systems DOT org CAcert Assurer "A perfect world is one of chaos." -- 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