Possible BSOD from getcwd on WinXP SP3
Hello, Building tar seems to trigger a Blue Screen Of Death on WinXP. I installed Cygwin (see attached for system information). I then downloaded the source for tar-1.22-1 and executed: cygport tar-1.22-1 compile 21 | tee /tmp/file The source code is unpacked and configure starts. During the configure step the machine blue screens. Upon reboot I look at the end of /tmp/file and I find: $ tail /tmp/file checking if environ is properly declared... yes checking for error_at_line... no checking for working fcntl.h... no (bad O_NOATIME) checking for struct stat.st_blocks... yes checking for working GNU fnmatch... no checking whether isblank is declared... yes checking whether __fpending is declared... no checking how to determine the number of pending output bytes on a stream... fp-_p - fp-_bf._base checking for fseeko... yes checking whether getcwd handles long file names properly... In /usr/src/tar-1.22-1/src and I find the results of the getcwd test: A very deep directory tree called conftest3 (conftest3/conftest3/conftest3/...) The source for conftest (conftest.c - attached) Compiled binary contest.exe In Cygwin attempting to cd to the bottom of the conftest3 directory tree will yield a BSOD. Running conftest.exe will yield a BSOD. A little experimentation with conftest.c shows the error happens during the creation of the directory tree. The Windows native tools are unable to correctly manage the conftest3 tree (I cannot remove it or descend to the bottom) 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. Thank you. -- George Henson Contractor, General Dynamics Information Technology Joint Medical Logistics Functional Development Center Email to: george dot henson2 at us dot army dot mil Cygwin Configuration Diagnostics Current System Time: Wed Jan 13 08:57:22 2010 Windows XP Professional Ver 5.1 Build 2600 Service Pack 3 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\PROGRA~1\Serena\vm\win32\bin C:\PROGRA~1\Serena\vm\common\bin\win32 C:\Program Files\Gradkell Systems, Inc\DBsign Data Security Suite\Common\Lib\ C:\WINDOWS\system32 C:\WINDOWS C:\WINDOWS\System32\Wbem C:\WINDOWS\system32\WindowsPowerShell\v1.0 C:\putty C:\Program Files\Tumbleweed\Desktop Validator\ C:\Program Files\ActivIdentity\ActivClient\ C:\sbin C:\Program Files\TortoiseSVN\bin C:\Program Files\Common Files\Roxio Shared\DLLShared\ C:\Program Files\Common Files\Roxio Shared\9.0\DLLShared\ C:\Program Files\ATI Technologies\ATI.ACE\ C:\Program Files\ApproveIt\ C:\Program Files\ApproveIt\ThirdParty\Bin\ C:\WINDOWS\system32\WindowsPowerShell\v1.0 C:\Program Files\GuardianEdge\GuardianEdge Clients\ Output from C:\cygwin\bin\id.exe UID: 11195(george.henson) GID: 10513(Domain Users) 0(root) 544(Administrators) 545(Users) 10513(Domain Users) SysDir: C:\WINDOWS\system32 WinDir: C:\WINDOWS USER = 'george.henson' PWD = '/home/george.henson' HOME = '/home/george.henson' Use '-r' to scan registry obcaseinsensitive set to 1 Cygwin installations found in the registry: System: Key: c5e39b7a9d22bafb Path: C:\cygwin a: fd N/AN/A c: hd NTFS152586Mb 13% CP CS UN PA FC d: cd N/AN/A t: net NTFS856763Mb 92% CP CS UN PA FC JWSRV07_DATA01 u: net NTFS856763Mb 22% CP CS UN PA FC JWSRV07_DATA02 x: net NTFS856763Mb 92% CP CS UN PA FC JWSRV07_DATA01 z: net NTFS 95354Mb 25% CP CS UN PA FC C:\cygwin/ system binary,auto C:\cygwin\bin/usr/bin system binary,auto C:\cygwin\lib/usr/lib system binary,auto cygdrive prefix /cygdrive userbinary,auto Found: C:\cygwin\bin\awk.exe Found: C:\cygwin\bin\awk.exe - C:\cygwin\bin\gawk.exe Found: C:\cygwin\bin\bash.exe Found: C:\cygwin\bin\bash.exe Found: C:\cygwin\bin\cat.exe Found: C:\cygwin\bin\cat.exe Found: C:\cygwin\bin\cp.exe Found: C:\cygwin\bin\cp.exe Found: C:\cygwin\bin\cpp.exe Found: C:\cygwin\bin\cpp.exe - C:\cygwin\etc\alternatives\cpp - C:\cygwin\bin\cpp-4.exe Not Found: crontab Found: C:\cygwin\bin\find.exe Found: C:\cygwin\bin\find.exe Found: C:\WINDOWS\system32\find.exe Found: C:\cygwin\bin\gcc.exe Found: C:\cygwin\bin\gcc.exe - C:\cygwin\etc\alternatives\gcc - C:\cygwin\bin\gcc-4.exe Not Found: gdb Found: C:\cygwin\bin\grep.exe Found: C:\cygwin\bin\grep.exe Found: C:\cygwin\bin\kill.exe Found: C:\cygwin\bin\kill.exe Found: C:\cygwin\bin\ld.exe Found: C:\cygwin\bin\ld.exe Found: C:\cygwin\bin\ls.exe Found: C:\cygwin\bin\ls.exe Found: C:\cygwin\bin\make.exe Found: C:\cygwin\bin\make.exe Found: C:\cygwin\bin\mv.exe Found: C:\cygwin\bin\mv.exe Found: C:\cygwin\bin\patch.exe Found: C:\cygwin\bin\patch.exe Found: C:\cygwin\bin\perl.exe Found:
Re: Possible BSOD from getcwd on WinXP SP3
Am 13.01.2010 16:18, schrieb Henson, George A CTR USA MEDCOM JMLFDC: A very deep directory tree called conftest3 (conftest3/conftest3/conftest3/...) The source for conftest (conftest.c - attached) Compiled binary contest.exe In Cygwin attempting to cd to the bottom of the conftest3 directory tree will yield a BSOD. Running conftest.exe will yield a BSOD. A little experimentation with conftest.c shows the error happens during the creation of the directory tree. The Windows native tools are unable to correctly manage the conftest3 tree (I cannot remove it or descend to the bottom) 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. Might this be simple filesystem corruption? If so, chkdsk might be your friend - give it a spin. -- 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
Re: Possible BSOD from getcwd on WinXP SP3
Henson, George A CTR USA MEDCOM JMLFDC George.Henson at amedd.army.mil 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. Cygwin is a user app, and as such, cannot cause a BSOD. Only 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. Meanwhile, you can work around it via: ./configure gl_cv_func_getcwd_path_max=yes to prime the cache and skip that check (I do that anyways on my XP machine, 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 handling makes the test spin for minutes at 100% CPU utilization, attributable to system call churn rather than application action). Also, that check is repeated among tar, coreutils, findutils, and a few other GNU packages. And for the record, I've also noticed that sysinternal's procexp can crash the system when trying to examine the run of that particular conftest.exe with very deep hierarchies. -- Eric Blake volunteer cygwin tar maintainer -- 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
volunteer solicited (was Re: Possible BSOD from getcwd on WinXP SP3)
On Wed, Jan 13, 2010 at 04:56:24PM +0100, Matthias Andree wrote: Am 13.01.2010 16:18, schrieb Henson, George A CTR USA MEDCOM JMLFDC: A very deep directory tree called conftest3 (conftest3/conftest3/conftest3/...) The source for conftest (conftest.c - attached) Compiled binary contest.exe In Cygwin attempting to cd to the bottom of the conftest3 directory tree will yield a BSOD. Running conftest.exe will yield a BSOD. A little experimentation with conftest.c shows the error happens during the creation of the directory tree. The Windows native tools are unable to correctly manage the conftest3 tree (I cannot remove it or descend to the bottom) 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. Might this be simple filesystem corruption? If so, chkdsk might be your friend - give it a spin. I think we need a BSOD FAQ entry. Anyone want to write one? cgf -- 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
Re: Possible BSOD from getcwd on WinXP SP3
On Wed, Jan 13, 2010 at 10:57 AM, Eric Blake e...@byu.net 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. Cygwin is a user app, and as such, cannot cause a BSOD. Only 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. Meanwhile, you can work around it via: ./configure gl_cv_func_getcwd_path_max=yes to prime the cache and skip that check (I do that anyways on my XP machine, 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 handling makes the test spin for minutes at 100% CPU utilization, attributable to system call churn rather than application action). Also, that check is repeated among tar, coreutils, findutils, and a few other GNU packages. And for the record, I've also noticed that sysinternal's procexp can crash the system when trying to examine the run of that particular conftest.exe with very deep hierarchies. -- Eric Blake volunteer cygwin tar maintainer -- 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 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 shi...@elite-systems.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
