X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4F1C0488.8020705@shaddybaddah.name> Date: Sun, 22 Jan 2012 23:43:52 +1100 From: Shaddy Baddah User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111114 Icedove/3.1.16 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: YA call for snapshot testing References: <20120119195244 DOT GA763 AT ednor DOT casa DOT cgf DOT cx> <20120121181804 DOT GA26978 AT ednor DOT casa DOT cgf DOT cx> <4F1B6F71 DOT 8070407 AT shaddybaddah DOT name> <20120122054719 DOT GB28773 AT ednor DOT casa DOT cgf DOT cx> <20120122055300 DOT GB657 AT ednor DOT casa DOT cgf DOT cx> <4F1BE5DF DOT 3010905 AT shaddybaddah DOT name> In-Reply-To: <4F1BE5DF.3010905@shaddybaddah.name> 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 Hi, On 22/01/12 21:33, Shaddy Baddah wrote: > You are right about the stack trace, as it is from the "first known > bad" snapshot, 2011-12-17. And it was wrong of me to use that > snapshot, as the "Bad address" errors don't occur with the latest > snapshot, 2012-01-11. It seems I spoke too soon. The behaviour under the latest snapshot is erratic. I thought it may be helpful to repeat the find, but without any -iname filter, just printing everything. The idea being to get an indication of whereabouts it is getting into trouble: sbaddah@*********** ~ $ uname -a CYGWIN_NT-6.1-WOW64 *********** 1.7.10s(0.259/5/3) 20120111 22:39:26 i686 Cygwin sbaddah@*********** ~ $ find ~/.. -print > sbaddah.20120111.lst 2>&1 Looking through the end of the file, I saw a return of the "Bad adddress" errors: ... /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/afro-debian.vmem find: `/cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/afro-debian.vmem.lck': Bad address /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/afro-debian.vmem.lck /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/afro-debian.vmsd /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/afro-debian.vmss /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/afro-debian.vmx find: `/cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/afro-debian.vmx.lck': Bad address /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/afro-debian.vmx.lck /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/afro-debian.vmxf /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/vmware-0.log /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/vmware-1.log /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/vmware-2.log /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/vmware.log /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/afro-debian/vprintproxy.log find: `/cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/dsl': Bad address /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/dsl find: `/cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/free-ubuntu': Bad address /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/free-ubuntu find: `/cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/puppy': Bad address /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/puppy find: `/cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/slitaz': Bad address /cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/slitaz find: `/cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines/temp-w2k': Bad address 1 [main] find 14244 C:\Users\Public\portapps\cygwin\bin\find.exe: *** fatal error - cmalloc would have returned NULL Stack trace: Frame Function Args 0028A3C8 6102F93B (0028A3C8, 00000000, 00000000, 00000000) 0028A6B8 6102F93B (6119CD20, 00008000, 00000000, 6119EB0F) 0028B6E8 61005E5C (6119E4A0, 0028B714, 00000006, 61002C47) 0028B708 61005E98 (6119E4A0, 6119E498, 00000001, 0028C9E0) 0028C9B8 61003154 (00000000, 00000000, 0028C9B4, 0028CAA8) 0028CBE8 610A828A (61267514, 0028CCC4, 0028CC48, 610816C0) 0028CC28 610A85DB (00000003, 00008000, 00000000, 6126A894) 0028CC48 610D34B5 (200384C0, 00000001, 00000001, 00000003) 0028CC88 00401FD6 (0000002F, 00000000, 612682FC, 61006E38) 0028CD28 61006E38 (00000000, 0028CD78, 61006430, 00000000) End of stack trace Then a repeat of the same command as before also resulted in "Bad address" errors, but without a crash: sbaddah@*********** ~ $ find ~/.. -iname '*dokan*' -print /cygdrive/c/Users/sbaddah/cygwin-home/../AppData/Local/Microsoft/Windows/WER/ReportArchive/AppCrash_dokansshfs.exe_92876bc78a1f772de610a09c818961eff3f197_1d68964b /cygdrive/c/Users/sbaddah/cygwin-home/../AppData/Roaming/Dokan /cygdrive/c/Users/sbaddah/cygwin-home/../AppData/Roaming/Dokan/DokanSSHFS /cygdrive/c/Users/sbaddah/cygwin-home/../AppData/Roaming/Microsoft/Windows/Recent/dokan-sshfs-0.6.0(2).zip.lnk /cygdrive/c/Users/sbaddah/cygwin-home/../AppData/Roaming/Microsoft/Windows/Recent/dokan-sshfs-0.6.0.zip.lnk find: `/cygdrive/c/Users/sbaddah/cygwin-home/../Documents/samsung/Kies/Podcast': Bad address find: `/cygdrive/c/Users/sbaddah/cygwin-home/../Documents/samsung/Kies/Ringtone': Bad address find: `/cygdrive/c/Users/sbaddah/cygwin-home/../Documents/samsung/Kies/Video': Bad address find: `/cygdrive/c/Users/sbaddah/cygwin-home/../Documents/SD16GB': Bad address find: `/cygdrive/c/Users/sbaddah/cygwin-home/../Documents/Virtual Machines': Bad address sbaddah@*********** ~ $ For what it's worth, this gives an indication of how far in to the find the crash occurs (by comparing filesize with the working 20111216 snapshot): sbaddah@*********** ~ $ ls -l sbaddah.20111216.lst sbaddah.20120111.lst -rw-r--r--+ 1 sbaddah Domain Users 37991442 Jan 22 23:10 sbaddah.20111216.lst -rw-r--r--+ 1 sbaddah Domain Users 24962125 Jan 22 23:09 sbaddah.20120111.lst Also for what it's worth, I am running one of the virtual machines for which .lck files exist. I thought this might suggest some type of Windows filesystem locking mechanism coming into play. However, there are "Bad address" errors encountered on other directories too, so I'm not so sure that that is a lead. -- Hope that helps, Shaddy -- 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