Re: issue report
Greetings, Stanislav Bivolarski! > C:\wamp\www\Leanplum-Marketing>grunt install > (node) sys is deprecated. Use util instead. > Running "exec:seedDB" (exec) task > 0 [main] sh 728 find_fast_cwd: WARNING: Couldn't compute > FAST_CWD pointer. Please report this problem to > the public mailing list cygwin@cygwin.com Please do not report issues in versions of Cygwin years, if not decades, old. Only the current version is supported. >>> 0 [main] sh 728 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. >>> Please report this problem to >>> the public mailing list cygwin@cygwin.com >>> tools/db_create.sh: line 3: $'\r': command not found > : No such file or directory 4: tools/config.sh >>> Exited with code: 1. > Warning: Task "exec:seedDB" failed. Use --force to continue. > Aborted due to warnings. > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html Also this ^ P.S. And as a general rule, "paste error text in google first". -- With best regards, Andrey Repin Tuesday, August 23, 2016 13:01:51 Sorry for my terrible english... -- 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: issue report
Objective Systems, Inc. REAL WORLD ASN.1 AND XML SOLUTIONS Tel: +1 (484) 875-9841 Fax: +1 (484) 875-9830 Toll-free: (877) 307-6855 (USA only) http://www.obj-sys.com On 8/22/2016 6:58 AM, Stanislav Bivolarski wrote: C:\wamp\www\Leanplum-Marketing>grunt install (node) sys is deprecated. Use util instead. Running "exec:seedDB" (exec) task 0 [main] sh 728 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com 0 [main] sh 728 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com tools/db_create.sh: line 3: $'\r': command not found : No such file or directory 4: tools/config.sh Exited with code: 1. Warning: Task "exec:seedDB" failed. Use --force to continue. Aborted due to warnings. I encountered this error right after I upgraded my workstation to Windows 8 or 8.1 (I can't remember which). Installing the most recent Cygwin got rid of it for me. Regards, Doug Coup -- 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 -- 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
issue report
C:\wamp\www\Leanplum-Marketing>grunt install (node) sys is deprecated. Use util instead. Running "exec:seedDB" (exec) task 0 [main] sh 728 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com >> 0 [main] sh 728 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. >> Please report this problem to >> the public mailing list cygwin@cygwin.com >> tools/db_create.sh: line 3: $'\r': command not found : No such file or directory 4: tools/config.sh >> Exited with code: 1. Warning: Task "exec:seedDB" failed. Use --force to continue. Aborted due to warnings. -- 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: Cygwin | Cygwin Compatibility Issue report ID 386608.
Hi Anuja Singh, thanks for your input! Just for you information, cygwin AT cygwin DOT com is a *public* mailing list, publically archived at http://cygwin.com/ml/cygwin/ This mailing list is the right forum for Cygwin bug reports and discussions, but be aware that your company disclaimer has no meaning at all here. Technical reply below. On Apr 27 00:05, Anuja Singh (MP Tech Consulting LLC) wrote: Hi Cygwin Support, [...] Tester/Developer Notes: Cygwin manually scans ntdll.dll to find the address of the global variable used to access the current working directory. It fails to do this on Windows 8, hence theerror every time the DLL loads. The error of this function is as follows: find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Thanks for the report. It had been fixed for the Developer Preview, but I just saw that it is broken again for the Consumer Preview. I'll take a stab at fixing that in the next couple of days. Cygwin is taking a direct dependency on a global variable in ntdll.dll which will likely break the app every time the DLL revs. You should consider using other methodsto maintain compatibility. Yes, we search for this variable manually, and we are aware that an upstream change in ntdll.dll might break Cygwin in this regard. Fortunately, if Cygwin can't find this global variable, it has a backup method to set the CWD as it needs to, so CYgwin applications will run, nevertheless. Please let me explain the motivation behind using this undocumented global variable. Keep in mind that Cygwin is a POSIX emulation layer, so there are certain expectations from the application's point of view. The only call in the Win32 subsystem to change the CWD is SetCurrentDirectory. SetCurrentDirectory has a couple of disadvantages: - SetCurrentDirectory only supports paths of up to MAX_PATH - 1 chars, including a trailing backslash. That's an absolute restriction, even when using the UNICODE API (static buffer). Cygwin supports up to 32K paths, just like the UNICODE API usually does. - SetCurrentDirectory fails for directories with strict permissions even for processes with the SE_BACKUP_NAME privilege enabled. The reason is apparently that SetCurrentDirectory calls NtOpenFile without the FILE_OPEN_FOR_BACKUP_INTENT flag set. An admin user should be able to chdir into any directory. - SetCurrentDirectory does not support case-sensitivity. Cygwin does. - Unlinking a CWD fails because SetCurrentDirectory calls NtOpenFile without the FILE_SHARE_DELETE sharing mode set. Cygwin supports this notion. Therefore we decided to do without SetCurrentDirectory and to manipulate the CWD manually. In the first place, the CWD handle is created with FILE_SHARE_DELETE sharing mode and with the FILE_OPEN_FOR_BACKUP_INTENT flag set. This worked fine up to Windows Server 2003 R2. But it broke with Windows Vista in a subtil way. It turned out that Vista introduced some structure we call struct FAST_CWD. The problem now being that the CWD handle is not only stored in the RTL_USER_PROCESS_PARAMETERS block, but additionally in a dynamically allocated FAST_CWD block. To make a long story short, unfortunately this structure and how to access it is not documented, nor is the global variable keeping its address exported from ntdll.dll. Obviously, we didn't want to drop the much more POSIX-like behaviour of Cygwin's chdir call with Vista. So the result was that we added code to figure out where the global variable is stored, plus a heuristic which tries to evaluate the layout of the FAST_CWD structure. All the code to do this you can find in the CVS repository, in the file path.cc: http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/path.cc?rev=1.661content-type=text/x-cvsweb-markupcvsroot=src starting at about line 3500. The structure layout is defined in cygheap.h: http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/cygheap.h?rev=1.158content-type=text/x-cvsweb-markupcvsroot=src at about line 220. So we are willing to keep this code in shape, even if the layout of the code and the structure changes again. However, I'm wondering if there is a chance that Microsoft could open up this part of ntdll.dll and export the global variable and document the layout of the structure we call FAST_CWD. Alternatively, if there is any other way to accomplish the above in an officially blessed way, we would certainly be eager to learn it. Is there a chance to discuss this issue with one of the developers or program managers of the kernel team? Thanks in advance, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info:
Re: Cygwin | Cygwin Compatibility Issue report ID 386608.
Hi Anuja, On Apr 27 12:15, Corinna Vinschen wrote: [...] Tester/Developer Notes: Cygwin manually scans ntdll.dll to find the address of the global variable used to access the current working directory. It fails to do this on Windows 8, hence theerror every time the DLL loads. The error of this function is as follows: find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Thanks for the report. It had been fixed for the Developer Preview, but I just saw that it is broken again for the Consumer Preview. I'll take a stab at fixing that in the next couple of days. FYI, I have fixed that in CVS: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/path.cc.diff?cvsroot=srcr1=1.661r2=1.662 The problem only occurs on Windows 8 CP 32 bit. It looks like the RtlEnterCriticalSection function has been inlined, so the Cygwin function searching the global FAST_CWD pointer, which expected a call to RtlEnterCriticalSection, didn't work anymore. WOW64 is not affected apparently. The remainder of my previous mail is still valid, though, and I'm looking forward to discuss this issue as outlined below. Cygwin is taking a direct dependency on a global variable in ntdll.dll which will likely break the app every time the DLL revs. You should consider using other methodsto maintain compatibility. Yes, we search for this variable manually, and we are aware that an upstream change in ntdll.dll might break Cygwin in this regard. Fortunately, if Cygwin can't find this global variable, it has a backup method to set the CWD as it needs to, so CYgwin applications will run, nevertheless. Please let me explain the motivation behind using this undocumented global variable. Keep in mind that Cygwin is a POSIX emulation layer, so there are certain expectations from the application's point of view. The only call in the Win32 subsystem to change the CWD is SetCurrentDirectory. SetCurrentDirectory has a couple of disadvantages: - SetCurrentDirectory only supports paths of up to MAX_PATH - 1 chars, including a trailing backslash. That's an absolute restriction, even when using the UNICODE API (static buffer). Cygwin supports up to 32K paths, just like the UNICODE API usually does. - SetCurrentDirectory fails for directories with strict permissions even for processes with the SE_BACKUP_NAME privilege enabled. The reason is apparently that SetCurrentDirectory calls NtOpenFile without the FILE_OPEN_FOR_BACKUP_INTENT flag set. An admin user should be able to chdir into any directory. - SetCurrentDirectory does not support case-sensitivity. Cygwin does. - Unlinking a CWD fails because SetCurrentDirectory calls NtOpenFile without the FILE_SHARE_DELETE sharing mode set. Cygwin supports this notion. Therefore we decided to do without SetCurrentDirectory and to manipulate the CWD manually. In the first place, the CWD handle is created with FILE_SHARE_DELETE sharing mode and with the FILE_OPEN_FOR_BACKUP_INTENT flag set. This worked fine up to Windows Server 2003 R2. But it broke with Windows Vista in a subtil way. It turned out that Vista introduced some structure we call struct FAST_CWD. The problem now being that the CWD handle is not only stored in the RTL_USER_PROCESS_PARAMETERS block, but additionally in a dynamically allocated FAST_CWD block. To make a long story short, unfortunately this structure and how to access it is not documented, nor is the global variable keeping its address exported from ntdll.dll. Obviously, we didn't want to drop the much more POSIX-like behaviour of Cygwin's chdir call with Vista. So the result was that we added code to figure out where the global variable is stored, plus a heuristic which tries to evaluate the layout of the FAST_CWD structure. All the code to do this you can find in the CVS repository, in the file path.cc: http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/path.cc?rev=1.661content-type=text/x-cvsweb-markupcvsroot=src starting at about line 3500. The structure layout is defined in cygheap.h: http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/cygheap.h?rev=1.158content-type=text/x-cvsweb-markupcvsroot=src at about line 220. So we are willing to keep this code in shape, even if the layout of the code and the structure changes again. However, I'm wondering if there is a chance that Microsoft could open up this part of ntdll.dll and export the global variable and document the layout of the structure we call FAST_CWD. Alternatively, if there is any other way to accomplish the above in an officially blessed way, we would certainly be eager to learn it. Is there a chance to discuss this issue with one of the developers or program managers of the kernel team? Thanks in advance, Corinna Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin
Re: Cygwin | Cygwin Compatibility Issue report ID 386608.
On Fri, Apr 27, 2012 at 12:15:19PM +0200, Corinna Vinschen wrote: Just for you information, cygwin AT cygwin DOT com is a *public* mailing list, publically archived at http://cygwin.com/ml/cygwin/ This mailing list is the right forum for Cygwin bug reports and discussions, but be aware that your company disclaimer has no meaning at all here. And, in fact, company disclaimers are not permitted per site policy. 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
Cygwin | Cygwin Compatibility Issue report ID 386608.
Hi Cygwin Support, I am a Program Manager with the Ecosystem Engineering team at Microsoft. At Mobile World Congress in February, Microsoft announced the availability of the Windows 8 Consumer Preview. Please use the resources available at the Windows Development Center and begin testing your applications. For more information on how to verify the compatibility of your applications on Windows 8 Consumer Preview, please refer to the Windows and Windows Server 8 Consumer Preview Compatibility Cookbook. Our team drives the bug notification activity with our valued Windows partners. This email is to notify you that Cygwin experienced compatibility issue during internal Microsoft testing. Please review the details provided below with regard to this issue. Compatibility Issue details: Product name: Cygwin Description of the Problem: Xserver does not load Detailed Steps to Reproduce the Problem: 1. Click on CygwinX 2. Observe that there is no response 3. Click on Cygwin rxvt 4. Observe that an error is generated in the background Expected Result: CygwinX and Cygwin rxvt renders successfully. Actual Result: CygwinX and Cygwin rxvt loads successfully. Tester/Developer Notes: Cygwin manually scans ntdll.dll to find the address of the global variable used to access the current working directory. It fails to do this on Windows 8, hence theerror every time the DLL loads. The error of this function is as follows: find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Cygwin is taking a direct dependency on a global variable in ntdll.dll which will likely break the app every time the DLL revs. You should consider using other methodsto maintain compatibility. If you are not the appropriate contact for this issue, please connect us with that individual as soon as possible. Please let me know if you have any questions and thank you for your continued engagement with Microsoft. Best regards, Anuja Singh Program Manager Microsoft PC Ecosystem Engineering v-anu...@microsoft.com REF ID: 386608 This communication is intended to be shared only with the indicated recipient(s). The information contained in this communication and any attachments to this are confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by the response to this communication and delete the original information you have received. -- 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: Cygwin | Cygwin Compatibility Issue report ID 386608.
Dear Microsoft, Which version did you test? See the following thread: http://cygwin.com/ml/cygwin-developers/2011-10/threads.html#5 Re: Add support for Windows 8, first step Regards, Nick On Fri, Apr 27, 2012 at 1:05 AM, Anuja Singh (MP Tech Consulting LLC) v-anu...@microsoft.com wrote: find_fast_cwd -- 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
