My system is Windows 7 professional 64 bit. The Cygwin is 32 bit, updated monthly
I have a backup script that used to run successfully from a Windows shortcut or scheduled task as C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c "/home/gulliver/bin/backup >> /cygdrive/c/temp/backup.log 2>&1" However, around August 2013 this stopped working (it took me a while to notice) If I try in a windows command prompt it also crashed, I get a small run.exe.stackdump file: Stack trace: Frame Function Args 00284B28 610303D2 (00000114, 0000EA60, 000000A4, 00284B78) 00284C38 610DA4DD (00000000, 00650000, 00284C78, 0028CE64) The problem is not with the bash command or script - it runs fine from both the command prompt or a shortcut if I change the command to C:\cygwin\bin\bash.exe -l -c "/home/gulliver/bin/backup >> /cygdrive/c/temp/backup.log 2>&1" but then there is an empty Windows window open for the whole time. A related issue is an xterm shortcut that used to work: C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c "xterm.exe -title TTTTT -bg '#EEFFFE' -e ssh -Y xxxx@yyyy&" This used to work as intended. Now it opens an xterm on the local host only - the ssh command fails. Again, removing the "run" and executing "bash" directly works but opens a second window. Does anyone know what might be happening or how to debug this problem? Thanks Gulliver -- 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