Re: Bug to setup Cygwin on Windows Server 2008 64bits
Kyeto schrieb: Corinna Vinschen-2 wrote: On May 7 01:48, Kyeto wrote: Hi, I have already installed Cygwin on several computers on 32 bits. But now, i need to setup it on my Windows Enterprise Server 2008 64bits. During the setup, there is no error. But when i lunch Cygwin, i have some exception which shutdown cygwin. (look the screenshoot) http://www.nabble.com/file/p23422628/Picture%2B2.png And in the file bash.exe.stackdump : Exception: STATUS_ACCESS_VIOLATION at eip=0043AF00 eax= ebx= ecx=61106EC8 edx= esi=611021A0 edi=0045A190 ebp=0027CC98 esp=0027C65C program=C:\cygwin\bin\bash.exe, pid 3396, thread main cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B Stack trace: Frame Function Args 0027CC98 0043AF00 (0001, 011601B0, 01160090, 61010E8C) 0027CD68 610060D8 (, 0027CDA0, 61005450, 0027CDA0) 61005450 61004416 (009C, A02404C7, E8611021, FF48) 82763 [main] bash 3396 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 85226 [main] bash 3396 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) How can i resolv this problem ? I have search on different forum but i don't find any answer. This could be an issue with Terminal Server. If you installed TS on that machine, as a temporary workaround, switch off DEP. For the mid term we have a tool called peflags/peflagsall (in the rebase package) which allows to set the TS-awareness flag in executables. This will get rid of the problem (just use it from ash, which isn't affected by the problem for some reason). For the long term we will get a new gcc-4 at one point which sets the TS-awareness flag for newly created executables automatically. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ I have disabled DEP and now Cygwin run. But i have just the pompt with : bash-3.2$ : _ None commands are available When i do a "ls" => command not found. It's the same for a lot (touch, chmod ...) But, pwd, cd work Did you add C:\cygwin\bin into your PATH envrionment variable? pwd and cd are builtins, but touch, chmod and so on are executeables. Stefan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: 1.5.25: cygwin executeables are crashing from time to time (Windows 2003 Server Ver 5.2 Build 3790 Service Pack )
Mark Geisert schrieb: Stefan Walter writes: Attached now the cygcheck.out. Maybe someone can give me now a hint for the crashes. Additional: There is no Antivirus as well as Firewall running on the System. [...] Cygwin Configuration Diagnostics Current System Time: Tue Apr 14 11:02:39 2009 Windows 2003 Server Ver 5.2 Build 3790 Service Pack 2 Running under WOW64 on AMD64 Running in Terminal Service session Others may see something else in the cygcheck output you sent; thanks for sending it. What stood out to me is what's quoted above. This kind of smells like the "cygwin bash crashes on Win Serv 2008" thread from last October. That ended up with the realization that installing Terminal Service changes the system-wide DEP (Data Execution Protection) flag for the worse, as far as Cygwin is concerned. Could you please read one of the later emails on that thread: <http://cygwin.com/ml/cygwin/2008-10/msg00459.html> and see if the situation applies to your systems and whether the workaround works for you? I know the thread talks about Windows Server 2008 and you're running WS2K3, but maybe it applies there too. ..mark -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ I have changed the DEP as well as i was trying with peflags. Nothing seems to work. I am getting a critical situation, if there is no fix available. Does anyone have some further tips, how to solve the problem? Thanks in Advance, Stefan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: MS-DFSR conflict with cygwin file permissions
Larry Hall (Cygwin) schrieb: Stefan Walter wrote: Larry Hall (Cygwin) schrieb: Stefan Walter wrote: If you redirect output in cmd.exe to a file (echo "Hello world..." >output.txt), then the file "output.txt" have the file permissions inherited from the parent folder. If you redirect output in bash.exe to a file, then the file permissions are restricted. I need this solved, because the current given permission conflict with the Microsoft DFSr. Is there a way to create files with permissions inherited from parent folder? Read the section about NT security in the User's Guide <http://cygwin.com/cygwin-ug-net/ntsec.html> and then try setting 'nontsec' in your CYGWIN environment variable <http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>. That was a great hint. I tried it now with "CYGWIN=nontsec tty" and the permission are as i wanted it. One more question with that. In the guides for "sshd" they always recommend "CYGWIN=ntsec tty". Do you expect a problem if i run with nontsec? Beyond the loss of the POSIX permissions, no. You should check your 'sshd_config' file and make sure 'StrictModes' is set to 'no' though. 'tty' is not required for 'sshd' The loss of the POSIX permissions is fine for me. But what is then the purpose of tty in the CYGWIN variable? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: MS-DFSR conflict with cygwin file permissions
Larry Hall (Cygwin) schrieb: Stefan Walter wrote: If you redirect output in cmd.exe to a file (echo "Hello world..." >output.txt), then the file "output.txt" have the file permissions inherited from the parent folder. If you redirect output in bash.exe to a file, then the file permissions are restricted. I need this solved, because the current given permission conflict with the Microsoft DFSr. Is there a way to create files with permissions inherited from parent folder? Read the section about NT security in the User's Guide <http://cygwin.com/cygwin-ug-net/ntsec.html> and then try setting 'nontsec' in your CYGWIN environment variable <http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>. That was a great hint. I tried it now with "CYGWIN=nontsec tty" and the permission are as i wanted it. One more question with that. In the guides for "sshd" they always recommend "CYGWIN=ntsec tty". Do you expect a problem if i run with nontsec? Stefan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
MS-DFSR conflict with cygwin file permissions
If you redirect output in cmd.exe to a file (echo "Hello world..." >output.txt), then the file "output.txt" have the file permissions inherited from the parent folder. If you redirect output in bash.exe to a file, then the file permissions are restricted. I need this solved, because the current given permission conflict with the Microsoft DFSr. Is there a way to create files with permissions inherited from parent folder? Regards Stefan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: 1.5.25: cygwin executeables are crashing from time to time (Windows 2003 Server Ver 5.2 Build 3790 Service Pack )
You need to read the problem reporting guidelines at: http://cygwin.com/problems.html But, I suspect BLODA: http://cygwin.com/acronyms/#BLODA cgf Thanks for your input. BLODA sounds not bad as a possible cause. Somehow i have to get rid of this problem, but dont know at the moment how to start with it? Is there any way that i can analyse this deeper? Please advise. Sorry if my question sounds stupid, but i am not very much experienced with cygwin, therefore i really need some help. Help us help you. We're not mindreaders here; we don't know anything about your system setup. Read what the first link above tells you to do and then do that. In particular send 'cygcheck -s -v -r' output **as an attachment** on your next email here. If you want to be really proactive, do what the first link above tells you to do then check your system for the existence of any of the BLODA listed in the second link above, or any program that might be similar to ones already on the list, regardless of your "not very experienced with Cygwin" opinion of whether it matters. It matters most to relative newbies such as yourself :-). ..mark -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ Attached now the cygcheck.out. Maybe someone can give me now a hint for the crashes. Additional: There is no Antivirus as well as Firewall running on the System. Thanks Stefan Cygwin Configuration Diagnostics Current System Time: Tue Apr 14 11:02:39 2009 Windows 2003 Server Ver 5.2 Build 3790 Service Pack 2 Running under WOW64 on AMD64 Running in Terminal Service session Path: C:\Program Files\HP\NCU C:\Program Files\Support Tools\ C:\Program Files (x86)\Windows Resource Kits\Tools\ C:\WINNT\system32 C:\WINNT C:\WINNT\System32\Wbem C:\WINNT\sysWOW64 C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\ C:\Program Files\Microsoft SQL Server\90\DTS\Binn\ C:\Program Files\Microsoft SQL Server\90\Tools\binn\ C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\ C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\ C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\ C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\ C:\cygwin\bin S:\lisecsw-srv\Common\x64 C:\Program Files\System Center Operations Manager 2007\ C:\Program Files\OmniBack\bin\ Output from C:\cygwin\bin\id.exe (nontsec) UID: 1005(liorder) GID: 513(None) 513(None) 544(Administrators) 545(Users) 1007(SQLServer2005DTSUser$WNDRPSQ90DE) 1009(SQLServer2005MSSQLServerADHelperUser$WNDRPSQ90DE) 1013(SQLServer2005NotificationServicesUser$WNDRPSQ90DE) Output from C:\cygwin\bin\id.exe (ntsec) UID: 1005(liorder) GID: 513(None) 513(None) 544(Administrators) 545(Users) 1007(SQLServer2005DTSUser$WNDRPSQ90DE) 1009(SQLServer2005MSSQLServerADHelperUser$WNDRPSQ90DE) 1013(SQLServer2005NotificationServicesUser$WNDRPSQ90DE) SysDir: C:\WINNT\system32 WinDir: C:\WINNT PWD = '/cygdrive/c/temp' CYGWIN = 'ntsec tty' HOME = '/home/liorder' HOMEPATH = '\Documents and Settings\liorder.WNDRPSQ90DE' APPDATA = 'C:\Documents and Settings\liorder.WNDRPSQ90DE\Application Data' PROGRAMW6432 = 'C:\Program Files' TERM = 'cygwin' PROCESSOR_IDENTIFIER = 'EM64T Family 6 Model 23 Stepping 6, GenuineIntel' WINDIR = 'C:\WINNT' COMMONPROGRAMW6432 = 'C:\Program Files\Common Files' USERDOMAIN = 'WNDRPSQ90DE' COMMONPROGRAMFILES(X86) = 'C:\Program Files (x86)\Common Files' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\Documents and Settings\All Users' TEMP = '/cygdrive/c/DOCUME~1/LIORDE~1.WND/LOCALS~1/Temp/9' COMMONPROGRAMFILES = 'C:\Program Files (x86)\Common Files' OMNIORB_CONFIG = 'S:\lisecsw-srv\Common\x64\omniORB.cfg' LIB = 'C:\Program Files\SQLXML 4.0\bin\' USERNAME = 'liorder' CLUSTERLOG = 'C:\WINNT\Cluster\cluster.log' PROCESSOR_LEVEL = '6' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' PROCESSOR_ARCHITEW6432 = 'AMD64' USERPROFILE = 'C:\Documents and Settings\liorder.WNDRPSQ90DE' CLIENTNAME = 'A00034858' LOGONSERVER = '\\WNDRPSQ90DE' PROCESSOR_ARCHITECTURE = 'x86' !C: = 'C:\temp' SHLVL = '1' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' HOMEDRIVE = 'C:' PROMPT = '$P$G' COMSPEC = 'C:\WINNT\system32\cmd.exe' TMP = '/cygdrive/c/DOCUME~1/LIORDE~1.WND/LOCALS~1/Temp/9' SYSTEMROOT = 'C:\WINNT' PROCESSOR_REVISION = '1706' PROGRAMFILES = 'C:\Program Files (x86)' NUMBER_OF_PROCESSORS = '8' PROGRAMFILES(X86) = 'C:\Program Files (x86)' SESSIONNAME = 'RDP-Tcp#190' COMPUTERNAME = 'WNDRPSQ90DE' !EXITCODE = '' _ = '/usr/bin/cygcheck' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\
Re: 1.5.25: cygwin executeables are crashing from time to time (Windows 2003 Server Ver 5.2 Build 3790 Service Pack )
> On Tue, Apr 14, 2009 at 05:39:20AM +0400, Stefan Walter wrote: >>The cygwin processes are crashing on the "Windows 2003 Server Ver 5.2 >>Build 3790 Service Pack". It does not happen regulary, just sometimes but >>then in series of lets say 5-10 exectuions. This happens on multiple >>machines, all with the same OS, therefore i think it is a bug rather than >>a setup problem. >> >>I have already removed cygwin and installed it fresh - this did not >> change >>anything. >> >>i have seen the crashes for: bash, sh, ls, cp, ... >> >>Here are some examples of the Windows Event Log: >> >>Faulting application cp.exe, version 0.0.0.0, faulting module >> cygwin1.dll, >>version 1005.25.0.0, fault address 0x00047699. >> >>Faulting application bash.exe, version 0.0.0.0, faulting module >>cygwin1.dll, version 1005.25.0.0, fault address 0x00047699. >> >>Faulting application ls.exe, version 0.0.0.0, faulting module >> cygwin1.dll, >>version 1005.25.0.0, fault address 0x00047699. >> >>NOTE: the address is always similar and points to something in the >>cygwin1.dll. >> >> >>Is there any workaround, or how can we fix this? This problem is critical >>for us. > > The fault address of 0x00047699 is not in the cygwin DLL. > > You need to read the problem reporting guidelines at: > > http://cygwin.com/problems.html > > But, I suspect BLODA: > > http://cygwin.com/acronyms/#BLODA > > cgf Thanks for your input. BLODA sounds not bad as a possible cause. Somehow i have to get rid of this problem, but dont know at the moment how to start with it? Is there any way that i can analyse this deeper? Please advise. Sorry if my question sounds stupid, but i am not very much experienced with cygwin, therefore i really need some help. Regards Stefan > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
1.5.25: cygwin executeables are crashing from time to time (Windows 2003 Server Ver 5.2 Build 3790 Service Pack )
The cygwin processes are crashing on the "Windows 2003 Server Ver 5.2 Build 3790 Service Pack". It does not happen regulary, just sometimes but then in series of lets say 5-10 exectuions. This happens on multiple machines, all with the same OS, therefore i think it is a bug rather than a setup problem. I have already removed cygwin and installed it fresh - this did not change anything. i have seen the crashes for: bash, sh, ls, cp, ... Here are some examples of the Windows Event Log: Faulting application cp.exe, version 0.0.0.0, faulting module cygwin1.dll, version 1005.25.0.0, fault address 0x00047699. Faulting application bash.exe, version 0.0.0.0, faulting module cygwin1.dll, version 1005.25.0.0, fault address 0x00047699. Faulting application ls.exe, version 0.0.0.0, faulting module cygwin1.dll, version 1005.25.0.0, fault address 0x00047699. NOTE: the address is always similar and points to something in the cygwin1.dll. Is there any workaround, or how can we fix this? This problem is critical for us. Regards Stefan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
