X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=cxzKXS6Lu5WC9B1t
	RsnLXn2Z2IVlt833koJrnofUBOg9pbM/ghEgUrlRf2GU0ZysuJ4LjBv7rcJVXmfC
	XGMSRye1EFaLA9ujVq2kV57mAdgGclLJzaDkMHVIGMlsZiUMx7j8niohA6xG7LoB
	L0viTX8pm6IRVIz/tlnUG2iJ/58=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=+v6ufs+y3+fT4F2GpQKqy7
	qvPyE=; b=DTbb3OmRonB3q3F+uH0ZdDawDDLJYqpddOahi8ZEbkAvD/+r/LE/P1
	7Z3H2fo0TCxy7EYTu1BfVlb9SmH81NDDEYww4jcy40+TKCLI+OhngsPvZ/szOmlM
	gS+C1KDZUsV6TYqgEIYbuRb5FuRX+sJH8t1alDprkSjk6UGkjs9nE=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: smtpback.ht-systems.ru
Date: Thu, 13 Mar 2014 00:19:57 +0400
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <1137274879.20140313001957@yandex.ru>
To: Gulliver Smith <gulliver DOT m DOT smith AT gmail DOT com>, cygwin AT cygwin DOT com
Subject: Re: Problems with run.exe (silent crashes) - stopped working suddenly
In-Reply-To: <CAK2rWZWGaAgKrqa0LUx7aWKXf8aTcAYCfQb3-oju8oK9664FUQ@mail.gmail.com>
References: <CAK2rWZWGaAgKrqa0LUx7aWKXf8aTcAYCfQb3-oju8oK9664FUQ AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Gulliver Smith!

> 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)

run is known to crash at random occasions, since... around that time.
I don't know if it has been fixed, sorry.
That aside, I see no reason to use run in your case.

> 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.

Use cron, then there won't be any stray windows.

> 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 AT yyyy&"

Now, THIS is a VERY wrong way to do it.
You're
1. Starting run
2. Telling it to start bash
3. Telling bash to start xterm
4. In which you're starting an SSH session.

Why not start xterm directly? Also, ever heard of PuTTY? Or mintty?

> 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?

Most simple solution would be to use right tools for the job, I'd say.


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 13.03.2014, <00:14>

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